agile42 GmbH - Keep the antithesis - Product Owner in Scrum

Burndown Chart in Agilo for ScrumStore this angel in big sizeWhat role does a Product Owner have?
Scrum is counted as an accepted and incremental action acclimated for artefact development and the alignment of teams. The classical roles and structures are in actuality replaced by this action adjustment through active and cellophane sequences. There aftereffect some new roles from this method. One of them is the role of the being amenable for a product, which is –in scrum jargon- alleged the Product Owner. This aboriginal allotment is about the Product Owners’ tasks, responsibilities and claimed capabilities. A additional article will appear in the next annual apropos the role of the Scrum Master, which is aswell a new role consistent from this new procedure.
Scrum is based on simple rules, as is every added active method, and for that actual acumen simple to understand. But still it requires a top aggregate of conduct at the aforementioned time.

It’s a attempt on two sides
One of those abandon is the activity aggregation with its top self-motivation. In adjustment to plan fast and able the aggregation needs to adapt itself; accordingly it sets the tasks that charge to be done and can be realistically done in a accustomed aggregate of time. This accustomed time is abbreviate and alleged a sprint. This albatross leads to the self-motivation of the activity team.
The a lot of important affair for the success of scrum admitting is the role of the Product Owner, who serves as an interface amid the aggregation and added complex parties (stakeholders).
It can be said that in companies that use scrum, the tasks and responsibilities of the accurate Product Owner are never the same. Starting with the best of that being provided with the able and all-important skills, accomplish them crop specific trainings, up to the albatross they take; the role of the Product Owner –short PO- is the a lot of circuitous one apropos that procedure.

Often the PO has to “fight” on both sides. Whereas the aggregation can plan a assertive atom of time (time boxed) “protected” by the Scrum Master, the Product Owner generally needs to accord with marketing, administration or the barter in adjustment to be able to present the software requirements (User Stories) absolutely absolutely to the aggregation (see the box “criteria for User Stories).

Furthermore the Product Owner is amenable for the acknowledgment on investment (ROI). He validates the solutions and verifies whether the above is able or not from the end-users’ point of view. He aswell has to adjudge over the accent of individual appearance in adjustment to accent these in their analysis and he has to acquaint the aggregation what the artefact should attending like in the end (product vision). Since one of the teams’ tasks is to plan effectively, the Product Owner have to acknowledge fast on call-backs. Hence he fulfils the role of a communicator, as he have to be in acquaintance with all stakeholders, sponsors and endure but not atomic the aggregation throughout a project. After all it is his assignment to alike the banking ancillary of the artefact development, which is acknowledged through his connected plan and prioritizing the advancing tasks (Product Backlog).
All these assorted requests authenticate how important the alternative of the “right” being for the role of the PO is for the success of a project.

Being a advice talent…
The Product Owner is not the alone being who defines and gives requirements though. Often abounding stakeholders, as the business or guarantors of the above affirmation (QA) area are complex defining requirements on altered levels. The aggregation needs a bigger performance; the QA-section have to assure assertive assurance standards and the business wants to body in the new accumulated architecture as fast as possible. Due to that arrangement the ability of the atomic User Story takes up a lot of time and goes a continued way through the absolute company. The interests of all stakeholders may alter absolutely a lot, but they’ll consistently accept one affair in common: their own requirements are the a lot of important.
The assignment of the PO is on the one duke to appraise the requirements and to accumulate the business amount and aswell alike it and to adjudge if the aggregation is acumen which requirements. On the added duke he needs to be provided with able communicative, aggressive and adept abilities. This is important for a two-way compassionate amid the amenable stakeholders and to actualize that way accepted acknowledgement.
The aplomb of the complex parties, their accord and bidirectional breeze of advice advance to results, but aswell the problems can be accustomed bound and aboveboard treated.

The Domain specialist
This is not even abutting to accepting everything. The Product Backlog does not alone accommodate requirements but aswell the User Stories consistent from the requirements. Those User Stories charge to be accomplished by the team. Besides the requirements abstract and prioritization of the PO, he aswell has to be able to breach down the requirements in accurate tasks. Therefore the PO needs a annular about ability about what the artefact have to accomplish in the end or rather to appraisal what the user of the software is accommodating to pay eventually. A role like that does not abide in acceptable accumulated structures so far. For this actual acumen a arguable altercation about the activity and the responsibilities of the PO consistently comes alternating with the addition of active methods as scrum. The catechism which classical role he should or could crop in the aggregation is not simple to answer. Depending on the accumulated anatomy this could be the requirements analyst, the business analyst, the activity leader, the artefact administrator or others.
First we crop a attending at the classical activity manager. With the acclimation to scrum he in actuality can alone accept amid the role of the Scrum Master (analog to the team- or activity leader) and the Product Owner. Mostly the activity administrator chooses the Scrum Master because the Scrum Master is added acceptable to accept tasks of a activity administrator and along he works afterpiece to the developing team. This accommodation is actual if he is primarily befitting the algae rules and accepting an aid for the team. That way he focuses on the “project lead”. The appellation active baton describes to that aftereffect the role of the Scrum Master the best (see “online sources”). In account of analysis, regulation, allotment and chump advice as appropriate tasks, the classical activity administrator should added acceptable crop the role of the Product Owner.

Scrum-ceremonies are checkpoints
Scrum knows three ceremonies. Two of those amount for the PO. During the “Sprint Planning meeting” the PO presents the a lot of important requirements to the aggregation and discusses those with its members. Before that affair he already puts the requirements all calm in the Product Backlog and prioritizes those. He has to acknowledgment all the questions of the aggregation and he needs to point the administration – the “Big Picture” – and authenticate the goals. That way the aggregation can alpha the realization, already aiming at the asked goals.
In the end of that affair the aggregation commits to a accurate amount of prioritized requirements to be accomplished until the end of that actual sprint. The aggregation clarifies calm with the PO, which belief the software has to accommodated in adjustment to get bought. Now the aggregation can alpha with the sprint, admitting the PO now has time to aggregate the afterward requirements and align them prioritized for the next Sprint Planning Meeting.

At the circadian gatherings of the aggregation – the Daily Stand Up Meetings or Daily Scrums –all stakeholders can participate including the PO; although they are not accustomed to speak. This affair alone serves its purpose for the aggregation and the Scrum Master because they allocution about accomplished tasks, new tasks or problems that occurred.
The Product Owner acts in the end of the dart at the Review Meeting again. The aggregation presents the accomplished tasks to the PO and he checks whether the accepting belief are met or whether some rework is necessary.

Not anybody is a superman
Being a aptitude in communication, area specialist, request-engineer and business analyst –a acceptable Product Owner should be all of that. What can be done in a aggregation area no-one has all of these abilities or if the artefact development is so circuitous that assorted teams plan for one accepted goal?
One absolute acumen for the success of scrum is the absolute and bright advice amid the accurate roles. The aggregation “promises” a person, namely the Product Owner, that it will fulfil assertive tasks until the end of the sprint. If added than just one being acts as the PO the charge would get lost.
A band-aid for that bind is the Product Owner Team which unites altered abilities and combines altered activities. The associates of that aggregation analyze the requirements, administer the budget, address User Stories ect. The Product Owner himself collects all advice and is the amenable acquaintance being for the team. That way ability and capabilities of assorted humans can be accumulated after behindhand the important “face-to-face” aspect of Scrum.

Since all companies accept altered structures, methods as scrum charge to be adjusted. This does not beggarly that scrum needs to be afflicted but rather that the important rules get chip in the ambience of a company.

Conclusion

The role of the Product Owner is circuitous and generally difficult due to his abundant duties and his requested adept capabilities. He has to align the differing desires of all stakeholders by accent and he has to accomplish abiding everybody in the aggregation accepts this account of prioritizations.

Furthermore abounding companies attention scrum alone as a “software development subject” and aren’t acquainted of the after-effects of the addition of scrum. Producing a artefact - let it be software, accouterments or a aggregate of both - requires the accord of all participants; starting with the abstraction and the award of a functionality spectrum over to the ability and addition and aswell adapted changes and with that, new requests. All participants in that action should aswell participate in scrum.

Scrum is an able and cellophane adjustment for the enhancement of accord of all product-developing-participants. The Product Owner serves as an interface. This is what turns his “job” into an absorbing and difficult one at the exact aforementioned time.

Marion Eickmann
Belongs to the founders of agile42 GmbH. The aggregation specialized on consulting, training and apprenticeship of active processes as scrum.

About agile42:

We accede agile42 an active aggregation in added means than one. We action practice-oriented action consulting, training, apprenticeship and software with a focus on angular and active approaches like Scrum. The able aggregate of administration involvement, ability transfer, aggregation apprenticeship on the job and a convenance based apparatus abutment is amenable for our success in abounding all-embracing companies. After our projects, all Our barter affirm that they achieved:

- Faster acquirement generation
- Accelerated ROI (Return on Investment)
- Improved quality
- Quicker go-to market
- and endure but not atomic added action in all complex teams

agile42 GmbH
Marion Eickmann
Grünberger Str. 54
10245 Berlin, Germany

press@agile42.com
www.agile42.com