top of page
  • Writer's picturePaul Gravina

Agile/Scrum and Traditional PM-Scope/Change Control

Using the waterfall methodology all of the project's scope gets unidentified at the beginning of the project by using all the requirements gathered by the business/stakeholder. We (the business) want to get every single requirement out, documented and upfront, because we know how much changes will cost the business using this type of project methodology, with everything defined up front=changes$$$$$. So the business/stakeholder asks for it all, anything and everything that they can think of and get in so they can cost it at the beginning of the project, again changes, later on, will cost them plenty. Scrum loves to change the teams and lives by embracing change, delivering working software with every iteration after every sprint keeps the costs down, keeps development working as a team, keeps software time-boxed for delivery cycles, and documents good engineering practices thus saving time=$$$$$. With the business/project owner sitting in on all the meetings throughout the entire scrum, will result in NOT building lots of features that will not be used (front loading), they prioritize the features most important to the business and store them in the product backlog working through each prioritized task that has been assigned to each sprint. You must involve, educate, teach and train the business/stakeholder in the framework (agile/scrum) and include them in the team. Scope Change Differences 1. Waterfall-Fill out a formal change control form for all requests. Scrum-Product Owner prioritizes the features. 2. Waterfall-Present change requests to the internal project change control team. Scrum-There is not a specific change control team, the scrum team handles backlog requests face to face with the product owner. 3. Waterfall-If the request is routine, lead the project change control team to a final decision. Scrum-Discussions about project additions (scope/features) are controlled by the business/stakeholder. 4. Waterfall-Communicate all change request decisions, approved and denied, to the project stakeholders. Scrum-Communication is done daily in stand-ups and always face to face, with no mixed messages. 5. Waterfall-File all documentation in the scoping plan. Scrum-All documentation is for all to see, on a whiteboard, wiki, 3x5 cards, nothing is filed away, transparency is key throughout the organization.

Owls Nest Capitals discussion on Agile/Scrum and Traditional PM-Scope/Change Control
Agile/Scrum and Traditional PM-Scope/Change Control

1 view0 comments


bottom of page