PRODUCT OWNER

1. To communicate with DevTeams as clear as possible,

2. To describe the requirements and product vision to DevTeams as precise as
needed,
3. To micro-manage the project or to allow the DevTeam self-organisation,
4. To handle locally distributed DevTeams appropriately,
5. To manage the product development project waterfallor agile driven like.
6. Product mgmt (PO) decides which product (model) of the
Lego kit the DevTem has to build
7. PO has the building description
8. DevTeam has Lego bricks only, and no building description
9. PO is not allowed to show construction plan or photos to DevTeam;
PO is allowed to inspect the plan as often she needs to;
10.How easy/difficult was your task? What were your emotions?
11.What made your task easy/difficult?
12.Were you stressed? Why?
13.How was the communication with DevTeam?
14.How often did you get back to view the instructions again?
15.How was it to be a micro-manager? To give the DevTeam trust and laissezfaire?
16.When is micro-management/waterfall appropriate and when agile
management?What were the experiences you made with locally distributed
teams?
17.How many deviations are between the final product (model) and the product
vision (building instruction.

SCRUM
The ideal agile team is a self organizing, dedicated, cross functional group
that has all the skills necessary to deliver a solution that solves their
customer's problem. As a result, the list of roles on an agile team is fairly

short generally consisting of roles such as Scrum Master, Product Owner, and
the Team. Given all that, many project managers wonder where they fit in.
They may act as the Product Owner if they have the skill set and decision
making authority to determine what the product should contain. They may
become the Scrum Master if they are able to practice servant leadership and
act as a coach and facilitator. They may become part of the team and help
develop or test. They may focus on coordinating the efforts of multiple agile
teams to support the broader goals of a large program. They may not be a
good fit for an agile environment at all. Join Kent McDonald as he describes
the Product Owner and Scrum Master roles in an agile environment and
discusses the various ways that project managers can assess their skill sets
and project characteristics to determine where they fit into the picture.
Learning Objectives:

Understand the roles and responsibilities of Product Owner and Scrum

Master (Agile Coach) in agile teams

Understand where the traditional project management responsibilities

are handled in agile projects

Learn how to determine where you fit on your next agile project.

TEAM
Commit to deliver product increments in each iteration
Meet commitments
Determine the size of user stories
Select the processes used to deliver value to customers
Reflect and adapt on process and product on a regular basis
Establish and agree to a definition of done for product increments
Decide on and maintain a sustainable pace
Hold each other accountable to meet team commitments
Help remove bottlenecks
Includes everyone working on the project
Members should be full time
The team determines how the product is delivered and how the work is divided up
to do that based on the conditions at the time.
Cross-functional:
Programmers, testers, business analysts, etc.
Members should be full-time
May be exceptions (e.g., database administrator)
Teams are self-organizing
Ideally, no titles but rarely a possibility
Membership should change only between iterations