Webinar: Development with Agile, Waterfall and Agile-Waterfall Hybrid
Agile in waterfall
description
Transcript of Agile in waterfall
![Page 1: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/1.jpg)
To be agile in a waterfall setting.Some reflections from a successful case.
Fredrik Wiik
![Page 2: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/2.jpg)
2
Why an agile way of working?
• Fixed deadline and clear mission statement!(Auftragstaktik, Helmut von Moltke)
• If we don`t start coding very soon we miss the deadline!
• To learn from the feedback loops is crucial when building a world class system from scratch!
• A skilled team used to agile ways of working.
![Page 3: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/3.jpg)
3
Touch points.
• The important start.
• The interation with the waterfall process.
• Stakeholder communication.
• A dynamic approach to the product owner role.
• Take ownership over the acceptance process.
![Page 4: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/4.jpg)
4
The important start.
• Establish trust and align forces on how to execute.
• Make sure the team understands context and purpose to release the power of these knowledge workers!
• Story mapping a la Jeff Patton, building the first slice of the system.
• Initiate the sprint cycles!
![Page 5: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/5.jpg)
5
The interation with the waterfall process.• Project responsible for budget governed by waterfall
model, intial rough estimation from supplier.
• The requirement were kept on the mission statement level.
• Focus on describing how the project will work with requirement management throughout the project.
• For the delivery, roll-out and close down activities, business as usual (but do you really want to close now ).
![Page 6: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/6.jpg)
6
Stakeholder communication.
”We need to run a few sprints to understand our speed.”
Bi-weekly sprint videos! Broad user group. Focus groups evolve.
Business on board!
Cooperates with steering group.
![Page 7: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/7.jpg)
7
Our dynamic approach to the product owner role.
• Fact: Role descriptions stated who should decide upon IT requirements.
• At a minumum that person must agree on the acceptance criterias for the user stories and sign them off.
• Make sure persons with relevant input, influences how to evolve the solution.
![Page 8: Agile in waterfall](https://reader036.fdocuments.us/reader036/viewer/2022083002/558c0259d8b42ab25b8b45eb/html5/thumbnails/8.jpg)
8
Take ownership over the acceptance process.