Sprint – a short development circle time boxed to typically two week periods in which the development works to complete the user stories they committed to during Sprint Planning.
When I interview developers I ask a lot of questions. They tell me about the developer’s background, their aptitude and their ability to fit culturally within the team. There’s one question I always save for last because it tells me more holistically what that developer is all about. What’s the question? “How do you know[…]
Sprint Backlog – the collection of user stories committed to by the development team during the “How” meeting of Sprint Planning.
User stories start their lives as an unruly mess. They often have just the briefest of descriptions, no direction and no vision for what they will be when they mature and reach the status of Done. The skilled product owner or agilist responsible for grooming these user stories takes this rough form and elaborates it[…]
Very simply I want to illustrate the impact of multi-tasking. It has an impact on value delivered as well as satisfaction from stakeholders and customers. My very simple model consists of three features that each require three tasks that take one day per task to complete. Once a feature is complete it will deliver $100[…]
An effective Agile shop starts with a well groomed backlog of user stories. This means collecting all of the user stories the organization is asking for into the backlog. But where to start? Collecting anything is better than nothing but there are a few key data points that can really help when a user story[…]
I was first introduced to burn-down charts without knowing that’s what I was seeing. I was attending a monthly chapter meeting of the Project Management Institute (PMI) and the guest speaker was presenting his methods for tracking and managing projects. What he demonstrated fascinated me to the point that I contacted the Vice President of[…]
Mike Cohn has a great introduction to the concept of story points and how to think about them on his blog at MountainGoatSoftware.com. It is a brief introduction that gives a definition of story points, what factors go into determining story points, and how they should be used in relative estimation of effort. The article provides[…]
The Role of the Scrum Master The Scrum Master is responsible for keeping the process of Scrum flowing. They are the ones that facilitate the Ceremonies of Scrum, Maintain the Artifacts of Scrum, and Removes Obstacles that are blocking the progress of team members. It is the Scrum Master’s responsibility to ensure that the Product[…]
The Short Version Scrum is an agile methodology primarily focused on the delivery of software that increases the value of a product or organization. The Long Version Scrum breaks the mold of traditional waterfall development of software systems. In waterfall every step was monolithic and one directional. You worked and worked and worked on a[…]