saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
I might be wrong in my understanding, therefore need some help on this topic.
In scrum, we do not have official requirements gathering at the start. So we do not have WBS and so HOW does a manager estimates on cost and time in scrum ?
Also, how can a manager decide what is in scope and what is in not in scrum if requirements come in as and when given by customer ? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
See this: https://www.scrumalliance.org/community/ar...ow-scrum-works. I think it can help you. On the other side, keep focus on the definitions (WBS for example) and you will find those structures inside SCRUM and other methods. Saving Changes...
Krunal Naik, PMP,CSM,MBAProject Manager| https://www.linkedin.com/in/naikkrunalSouth Brunswick, Nj, United States
This is how I have done it in past. It may not be 100% srum and has some instances of lean startup and/or stage gate- but this was customized for organizational needs.
Product owner prepared prioritized list of business requirements(based on customer input/discovery phase) to create product backlog. Next step was sprint planning - resource(cost for SW), sprint timeline(4 weeks) and sprint backlog(to include scope for release worthy product) was finalized. After that we had sprint review and release to customer at the end of sprint. We followed same iteration for next few sprints to release final product.
You can also use traditional business cases documents and schedules as supporting documents if it helps you feel better for executive reviews and presentations.
Some references which may help,
https://www.scrumalliance.org/why-scrum https://www.mountaingoatsoftware.com/agile/scrum/overview https://www.atlassian.com/agile/scrum/ Saving Changes...
Chintan Jariwala, PMP, CSMProject Manager, IT Business Analyst| Sailfin Technologies India Pvt LtdSurat, Gujarat, India
I will briefly describe the rituals of Scrum. Following are the answers to your questions.
1. Requirement Gathering : We can do any type & level of work in Scrum in Sprints, No of days assigned to an Iteration. Thus, Many Scrum Team, mainly the Product Owner, organize a Sprint (vastly called "Sprint 0" ) to gather & document requirements.
2. Estimation : In Scrum, all the functionality are divided as User stories. In Scrum, we use Relative Estimation based on a benchmark. The time Unit is "Story Point". In Scrum, We do not estimate time for a Story, We estimate the size of the story. It is a very vast subject thus I will recommend to read the book "Agile Estimating and Planning" my Mike Cohn.
3. Scope Decision : The scope decisions are the subject & responsibility of Product Owner (PO). It is the PO who know the priority of the functionality. PO will decide which Users Stories will be completed in which Sprint. If the requirement is critical which comes in between a sprint, PO can change the scope of Sprint. Furthermore, In Scrum, Customers cannot directly interact with Scrum Team, they will interact with PO only. Thus, This responsibility lies on the PO. If he thinks that the functionality can wait till the next sprint, he will not change the scope.
I would recommend to read the books like "Essential Scrum: A Practical Guide to the Most Popular Agile Process" by Kenneth S. Rubin, "Succeeding with Agile: Software Development Using Scrum" by Mike Cohn.
I hope it helps. Saving Changes...
Al TaylorI.T. Contractor| IndependentWaterloo, Ontario, Canada
@Sergio, Krunal, and Chintan...thanks for your comments and links...very useful!....Al Saving Changes...
MAEN QADDOURAHProject Director| AJ SAUDIJeddah, Saudi Arabia
