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.
9th
SEP
Scrum Product Owner
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. I’ll begin by discussing the Product Owner because it is the most demanding of the roles.
In Scrum, the Product Owner is the one person responsible for a project’s success. The Product Owner leads the development effort by conveying his or her vision to the team, outlining work in the scrum backlog, and prioritizing it based on business value. Of course, he or she must also consider the stakeholders (to make sure their interests are included in the release) and the team (to make sure the release is developed by the deadline and within budget). As such, the Product Owner must be available to the team to answer questions and deliver direction.
But this combination of authority and availability to the development team makes it hard for the Scrum Product Owner not to micro-manage. Scrum values self-organization and, as a result, the Product Owner must respect the team’s ability to create its own plan of action. This means that a Product Owner is forbidden to give the team more work in the middle of the sprint. Even if requirements change or a rival organization unveils a new product that renders the team’s work all for naught, the Scrum Product Owner cannot alter the sprint until the next sprint planning meeting.
Furthermore, it is the Product Owner’s responsibility to consider which activities will produce the most business value. This means making tough decisions—that the team might not appreciate—during sprint planning. However, the Product Owner is the one person who must face the music if the project crashes and burns. Therefore, he or she must aggressively determine which features of a product are most important, when they are developed, etc. Just as the development team must produce the negotiated work for the Product Owner, the Product Owner must deliver the product to the customer.
posted by: scrum methodology
Comments Feed Reader's Comments
Leave a Reply
Newsletter Sign Up:
Recent Posts
- Results of an Agile Assessment
- Introduction to Scrum Video
- Complexity and cost of change
- Technical Debt – The High Cost of Change
- Strategic Vision and Scrum
- Agile and PPM – Q&A
- Estimating Earned Business Value on Agile Projects
- Building the Product Backlog
- Intro to Agile
- The Agile Manifesto and Twelve Principles
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Free Scrum Webinars
Categories
- Agile and Scrum (27)
- Agile Assessment (1)
- Agile Manifesto (5)
- Agile Principles (7)
- Scrum Basics (43)
- Scrum Discussion (26)
- Scrum Transitions (16)
- Uncategorized (7)
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- November 2010
- September 2010
- June 2010
- April 2010
- March 2010
- February 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 @ScottOstby
- Overheard from a Twitter post by @billportelli
- Overheard from a Twitter post by @iGuick
- Overheard from a Twitter post by @vigneshwaranr
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @CJ_381
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @CJ_381
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @dwinter
[...] I read about the roles in other agile approaches — Scrum Masters, Product Owners, Chief Architects, and Domain Experts — the essence of mentoring and passing on the way of [...]
[...] has three fundamental roles: Product Owner, ScrumMaster, and team [...]
[...] ett traditionellt Scrum-team är produktägaren den som prioriterar vad som ska utvecklas, den som har en vision om en produkt och den som ska [...]
“In Scrum, the Product Owner is the one person responsible for a project’s success.”
Seriously? I think this is seriously overstated. There is no one person responsible for a project’s success, regardless of whether you are doing waterfall or agile, scrum or XP.
There’s no question that there must be a Product Owner. But “the one person”? No.
There is a free Product Owner position description here http://www.clarus.co.nz/downloads/product-owner-job-description.html if it is of interest to anyone.
[...] most successful technique we implemented to get our Product Owners (PO) to increase their involvement with our Agile process was to encourage a ticket writing [...]
[...] has three fundamental roles: Product Owner, ScrumMaster, and team [...]