Scrum Methodology
Learn the Scrum Methodology
The Scrum methodology of agile software development marks a dramatic departure from waterfall management. In fact, Scrum and other agile processes were inspired by its shortcomings. The Scrum methodology emphasizes communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities — all attributes that suffer in the rigidly ordered waterfall paradigm.
10th
OCT
The Scrum Team Role
Posted by admin under Scrum Basics
There are three fundamental roles in the Scrum method of agile software development: the Product Owner, the ScrumMaster, and the team. In my last two articles, I discussed the roles and responsibilities of the Product Owner and the ScrumMaster. Now I’ll discuss the team and its function in Scrum.
In Scrum, an ideal team would include seven members, plus or minus two. Usually, teams are comprised of cross-functional members, including software engineers, architects, programmers, analysts, QA experts, testers, UI designers, etc. It is recommended all team members be located in the same room, called the team room.
While the development team must complete the work negotiated in the Sprint Planning Meeting, the team has some say in the amount of work it takes on. The Product Owner will expect the team to take on as many story points of work as possible, within reason. (The team would reference its established velocity for previous sprints to negotiate how many story points would be reasonable.) The value of this process of negotiation is twofold. It protects the development team from becoming swamped with an unrealistic workload. It also manages the expectations of the Product Owner, who, in turn, can do the same for customers.
Similarly, the team has the autonomy to determine how and when to complete its work. As long as the team finishes its work by the deadline and under budget, it is entirely up to the team to determine how that happens. Theoretically, the team could crank out all of its work in the first half of the sprint and spend the second half lounging at the beach, as long as the work satisfies the corresponding acceptance criteria. Granted, a team typically needs the entire sprint to complete its work. Actually, it’s not unusual for teams to discover within the first few days of a sprint, as analysis becomes less fuzzy, that it has more work to do than it realized at the sprint planning meeting. Furthermore, Scrum does not award partial credit. Even if 99 percent of a project is “done,” it will be rejected if it does not meet all the established acceptance criteria. A project’s finishing touches are often the most time-consuming and labor-intensive.
posted by: scrum methodology
Comments Feed Reader's Comments
Leave a Reply
Newsletter Sign Up:
Recent Posts
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Orlando Scrum Gathering in March 2010
- Free Scrum Webinars
- ScrumMaster as Impediment
- Advice for Agile Adoption
- Share Your Story
- Free Agile Resources
- Advice for Extending the Sprint
- Danube’s New Scrum Video Blogs
- What Happens at Scrum Training?
- The CSM Exam Saga Continues…
- The CSM Exam
Categories
- Agile and Scrum (18)
- Scrum Basics (33)
- Scrum Discussion (20)
- Scrum Transitions (9)
- Uncategorized (6)
Archives
- June 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
Blogroll
- Agile ALM
- Agile Methodology
- Agile Programming
- Agile Project Management
- Eric Brown
- Free Project Management Software
- IT Today
- PM Student
Danube on Twitter
- Overheard from a Twitter post by @sgamel
- Overheard from a Twitter post by @euro_latino
- Overheard from a Twitter post by @onion_soup
- Overheard from a Twitter post by @DarkSpooky
- Overheard from a Twitter post by @xiaoputi
- Overheard from a Twitter post by @jbuissing
- Overheard from a Twitter post by @andrewcmy
- Overheard from a Twitter post by @adrianoron
- Overheard from a Twitter post by @TheSoftwareGang
- Overheard from a Twitter post by @tshrinivasan

Hi. I am a long time reader. I wanted to say that I like your blog and the layout.
Peter Quinn
[...] of the trickiest problems that Scrum teams face is whether to allow a Product Owner to serve as a team member. Most Certified Scrum Trainers [...]
Thanks Peter! I love having you as a reader
Hi i am so pleased I found your blog, I really found you by mistake, while I was searching Yahoo for something else, At Any Rate I am here now and would just like to say thank you for a wonderful blog posting and a all round intriguing blog (I also love the theme/design), I do not have time to read it all at the right now but I have bookmarked it and also added your RSS feeds.