Saurabh JhaProject Manager| Pramati TechnologyChennai, Tamil Nadu, India
I want to know detail approach/best practices for managng scope in an Agile environment and how can we map PMBOK Scope Theories to Agile Saving Changes...
Sort By:
Klas SkogmarVice President and PMI R.E.P. trainer| Arkatay ConsultingMalmö, Sweden
In agile, the "collect requirements" is basically done by the Product Owner, who either channels requirements from stakeholders or comes up with new requirements from a user perspective. These requirements are usually in the form of "user stories", but can also be in other forms. User stories can be arranged in a hierarchical view, that then becomes the WBS for the project ("Create WBS"). The parent user stories are usually defined as Epics and/or Themes. In agile projects, scope is defined iteratively, so scope can be added even late in the project. "Define Scope" is usually done before each iteration starts, where each user story is detailedand acceptance criteria are defined for the contents of the iteration. Some aspects of "Define Scope" are also generally done on a release level or can be framed on a high-level for the entire project. "Validate Scope" is done continuously through TDD and additional testing is done at the end of each iteration, and sometimes at an additional iteration before a release. "Control Scope" is generally done through a burndown chart for an iteration and using a "burnup chart" to track scope for a specific release. Saving Changes...
Saurabh JhaProject Manager| Pramati TechnologyChennai, Tamil Nadu, India
Klas,
The explanation gave really nice clarity.
Many thanks.
