Project requirements management is what the Project Management Institute calls Project Scope Management and Scrum Alliance calls Product Backlog Management. The effort is to determine what all this hard work supposed to accomplish. The PMP Project Manager makes sure the project includes all the work required and only the work required by using complex processes and documentation. The Scrum Product Owner makes a list of everything that might possibly be needed and then evolves priorities and requirements by releasing finished product and seeing what happens.
Posts in this section focus on project management tools and techniques needed to effectively tame the requirements beast.
.
Second Stride – Getting Started with Agile Requirements
So, you have defined your product vision. You have gained approval to proceed with refining what the product should be. In other words, you will be determining what the requirements should be. In scrum terms that means creating the Product Backlog. Officially, the Product Backlog is a prioritized list of all the known requirements, desires, wishes, or glimmers to be included in [Continue Reading]
Seeing the Future – Scrum Product Vision Creation
To quote Ken Schwaber: "The minimum plan necessary to start a Scrum project consists of a vision and a Product Backlog. The vision describes why the project is being undertaken and what the desired end state is." (Schwaber 2004, p. 68). This is great, it seems so simple, a vision of what you want to build and a list of stuff that is needed to achieve that vision. Of course, [Continue Reading]
Toolmaking – Utility Excel Macros for Project Managers
We, as Homo sapiens, are toolmakers. This capability is one of the primary separators of our species from all of the others on the planet. We find a problem, a repeated action, something that annoys us to perform, and sooner or later, we start making devices, gadgets, and tools to make the task easier or go away entirely. Even with software, probably one of the most powerful [Continue Reading]
