You’re sitting in sprint review with your development team, and the product owner is presenting a new feature to you and the other stakeholders. Everyone is excited. You’ve been anxiously awaiting this feature. Maybe you have customers that have been expecting it, or better yet, you have a big sale that is depending on it.
When you're building your Scrum team, sometimes it doesn’t make sense for a particular individual to be a member of the team. They may have a specialty that’s only needed occasionally by the team or may be too busy with other work to participate in regular Scrum ceremonies.
When you're trying to put together a development team, you want to structure that team for success. It would be great to have all the perfect team members, but that dream cannot always be realized.
On September 20, 2018, Dave Todaro will join agile expert panelists for a fireside chat at the Quicken Loans Tech Con 2018 event. Dave is one of five technology leaders who will be gathering at the annual event in Detroit for discussion and Q&A about agile concepts.
You're all fired up about embracing agile software development and ready to build the ideal Scrum development team, but you’re not sure where to start. You might ask, "What is the perfect mix of team members needed to create my Super Scrum Development Team?"
As you build your Scrum toolkit, there are a few fundamental elements that are helpful for you and your team to understand on the path to developing an effective Scrum discipline. Scrum artifacts are the basic building blocks that allow you to plan, organize, and track the progress of your work.
I’ve found that the primary challenge in building software is, above all else, a communication problem. Someone needs to dream up what an application needs to do, and others need to build and test it. If there are communication issues along the way, that’s going to cost time.