- Product Owner
- Scrum Team
- Scrum Master
In some cases, the Product Owner and the customer are the same person; in
other cases, the customer might actually be millions of different people with a variety of needs.
The Product Owner role could map to the Product Manager or Product Marketing Manager position in many organizations.
The Scrum Team develop the product / project that the customer is going to use: (Software or website / web application)
For example. The team in Scrum should be “cross-functional”.
A team in Scrum is typically five to ten people, although teams as large as 15 and as small as 3 report benefits, and for a software project the team might include analysts, core developers,UI designers, and testers.
The ScrumMaster is one of the most important elements of Scrum success. The
ScrumMaster does whatever is in their power to help the team be successful.
for More info : read my previous article.
scrum-master-n-responsible
Hmm...nice topic
ReplyDelete1. Scrum is good only when team is really cross functional.
But do we really have people with these abilities? I doubt how are we going to change the attitude of team. Software people as been trademarked as Developer or tester. Developer doesn't want to do testing and testers doesn't want to do development.
They really don't have skill sets for cross functioning.
2. Scrum master is not a lead, he or she has own task for implementation so its really difficult for a SM to really track the Iteration or needs to compromise his/her own work.
3. Scrum is really not a dream kind of methodologies for clients they need project planning, estimations in advance before the project starts.
But agile/scrum works in small iteration.
will add more to disadvantages .....as soon as i get time
sir,
ReplyDeletethis article is really benifical. And the best part of small iterations are they are time bounded.I guess No other SDLC models consider the time factor. and another good thing i realized that 'retrospective meetings' after the completion of time bound of iterations.
But sir, at one thing i am confused that why we give points to the iterations in Fibonacci series manner. whats its need?? Or any one can give fake points for iteration.
please tell something about it.
Anoop, There are things :
ReplyDelete1) Estimation at story level
2) Estimation at task level
Story level estimation helps in project planning and determining the team velocity. Velocity means how much work a team can take in a Sprint. It will take couple of iterations to identify the team velocity. Points are just a Unit to estimates story. Same story could be different points for one person and could be different for another person. Story level estimation generally team members do based on the their skills, experience and complexity of the story.
It is not mandatory to use Fibonacci series, it could be different organization to organization or team to team.
Task level Estimations are which team does according to implementation, deployment or external dependencies etc..
Hope this will help to understand..
Thanks, now its clear .
ReplyDelete