SCRUM
-
Need help understanding....when SCRUM teams are set up? Once a project proposal has been accepted by the client, is this when the SCRUM team is put together and who is responsible for putting the team together? In the waterfall method, there is project scope (initiated by client) or we propose a concept, here we have the requirements phase and the necessary technical team help set the requirements and tool used....the proposal gets estimated ($$) by appropriate team members and if approved by client....development begins. How does SCRUM fit into all of this? Do we simply gather vague requirements from client and build SCRUM Team who then will clarify the requirements by defining how and what tools will be used, etc.?? How do projects get estimated in SCRUM before development begins?
-
Need help understanding....when SCRUM teams are set up? Once a project proposal has been accepted by the client, is this when the SCRUM team is put together and who is responsible for putting the team together? In the waterfall method, there is project scope (initiated by client) or we propose a concept, here we have the requirements phase and the necessary technical team help set the requirements and tool used....the proposal gets estimated ($$) by appropriate team members and if approved by client....development begins. How does SCRUM fit into all of this? Do we simply gather vague requirements from client and build SCRUM Team who then will clarify the requirements by defining how and what tools will be used, etc.?? How do projects get estimated in SCRUM before development begins?
vague requirements No Vague requirements .. With the JUST ENOUGH requirements , some baselined user stories are taken into account and the team can start the work.While the team is working on the user stories, the Scrum master, Product owner and the Stake holders can come up with new user stories , which will be put into Product Backlog. In a Scrum methodology, there is no need to gather all the requirements, design everything and start the work. There is a concept call JUST ENOUGH. Remember all the estimations should be made involving the team. The user stories can be anything , its not just coding and testing along... Like how and what tools will be used. The project estimation is based on Story points which signify the complexity of a user story. Let us say , 1 point Story = 2 Hrs = 2 hrs * $20 = $40 Thanks to my colleague, Sendhilraj who also contributed to this post.
Praveen Raghuvanshi Software Developer
-
vague requirements No Vague requirements .. With the JUST ENOUGH requirements , some baselined user stories are taken into account and the team can start the work.While the team is working on the user stories, the Scrum master, Product owner and the Stake holders can come up with new user stories , which will be put into Product Backlog. In a Scrum methodology, there is no need to gather all the requirements, design everything and start the work. There is a concept call JUST ENOUGH. Remember all the estimations should be made involving the team. The user stories can be anything , its not just coding and testing along... Like how and what tools will be used. The project estimation is based on Story points which signify the complexity of a user story. Let us say , 1 point Story = 2 Hrs = 2 hrs * $20 = $40 Thanks to my colleague, Sendhilraj who also contributed to this post.
Praveen Raghuvanshi Software Developer
Thanks for your response. I am still unclear of how the estimation works....in waterfall method each areas of expertise has already estimated ($$) the project after the business is awarded the team begins the work and after the project is completed we can view if our estimate was off. With SCRUM I understand the SCRUM Team will estimate the hours for the tasks selected for that sprint. But what about estimating the entire project as a whole. Customer would definitely want to see numbers before the project is awarded.
-
Thanks for your response. I am still unclear of how the estimation works....in waterfall method each areas of expertise has already estimated ($$) the project after the business is awarded the team begins the work and after the project is completed we can view if our estimate was off. With SCRUM I understand the SCRUM Team will estimate the hours for the tasks selected for that sprint. But what about estimating the entire project as a whole. Customer would definitely want to see numbers before the project is awarded.
Initially, estimation for the budget and time will be done by the experienced person(s) and it would be based on story points. once the project is approved, sprints will be discussed with the team and estimate it. Hope this helps!!!
Praveen Raghuvanshi Software Developer
-
Thanks for your response. I am still unclear of how the estimation works....in waterfall method each areas of expertise has already estimated ($$) the project after the business is awarded the team begins the work and after the project is completed we can view if our estimate was off. With SCRUM I understand the SCRUM Team will estimate the hours for the tasks selected for that sprint. But what about estimating the entire project as a whole. Customer would definitely want to see numbers before the project is awarded.
I have worked in Scrum team and i assure it is no way Waterfall model, rather mix of and more near to iterative model, v-model, spiral model,.. The rough estimation is usually done for a story first by product owner. Say a story is estimated with 8 hours of task. Then we distribute cards to team which have 7 cards each with 1,2,3,5,8,13,20. Each member tells his estimate for work. One on extreme side usually justify their estimates and we come to conclusion by discussion.