The guy in-charge of implementing Scrum at our office did an introductory session today at office. It creates a major break through from traditional project management by breaking up tasks in to manageable pieces, and short achievable deadlines. Tasks are generated in the form of User Stories and put up in the Product Backlog. A Product Owner will be responsible to prioritizing these user stories and will create a Release Backlog. A release backlog will have many Sprints which are either 2-4 weeks in length. The scrum team will be coached by a Scrum Master, who is in charge of driving the team. At the end of each sprint a working product should be available to show to the customer.
During the session many other colleagues asked their doubts and concerns over the process. I asked two questions for my part:
During the session many other colleagues asked their doubts and concerns over the process. I asked two questions for my part:
- If there is any particular feature request which the overall functionality could only be implemented for more than 4 weeks, how do we convince the customer?
Answer : No task can span more than 4 weeks. If there is such functionality it should be discussed with the team and should be broken into small chunks. Or such a sprint cannot continue.
2. Regarding stakeholders, there are two roles; Involving or Committing. Will a particular resource(ex: A developer) be assigned to multiple scrum teams in parallel?
Answer : No. Scrum doesn't permit.
There was a nice video shared by a colleague which gives a quick insight into Scrum:
No comments:
Post a Comment