The Product Owner asks how many Sprints IT will need to first figure out architecture and infrastructure issues. What are two options to explain how such work is managed using Scrum?
- After Some Small Experiments With Scrum (179.94 KiB) Viewed 198 times
(choose the best two answers)
A. You thank product management for understanding that these efforts indeed require effort and budget. You confirm that architecture and infrastructure are best addressed before starting Scrum, but that the exact budget is difficult to calculate upfront. You say you will organize this work in timeboxed Sprints of no more than 30 days to limit risk and be transparent toward product management on the actual progress.
B. You explain that product management should not worry about such typical IT work. You inform them that you will assure that the developers reach out to the right people within the IT organization when needed. During each Sprint Planning meeting they will keep the Product Owner updated about the additional effort it will take for that Sprint. That effort will come on top of the effort for the forecasted functional development.
C. You explain that technical risks are best controlled when architecture and infrastructure emerge alongside the development of functionality. The additional advantage is that business value is created faster and sooner.
D. You educate the Product Owner to add this work to Product Backlog to uphold transparency, have the Development Team estimate this and do this in early Sprints while also creating some business functionality in these early Sprints.