9. Start and Team Speed up
Product Owner Delivery Manager
Developers + QA
10. Role Definitions and Responsibilities
Product Owner
Responsible for the
product success.
Has the vision where
to take the product.
Empowered:
Owns the product in
behalf the Stakeholders.
Cares about the user
needs and the
business goals.
Team Player:
Developers + QA
and Stakeholders.
13. Role Definitions and Responsibilities
Delivery Manager
Line Management
Personal development and
performance assessment.
Stakeholder management
Develop good, strong relations
with the team’s key Stakeholders.
Delivery
With quality.
Agile best practices
Guarantee the use of
agile best practices.
People and culture
Create a fun, safe environment
worthy of the Paddy Power Betfair values.
Leadership
Provide guidance and steering.
Component ownership
Making sure that components
are correctly maintained and
have the adequate level of
monitoring and support.
Participate in product
development.
Commercial is strategic positioned to have all the feedback (Input) from different channels. This allow them to keep the focus on ideas generation to keep the costumers/users satisfied as well as increate the business revenue.
If the new feature is under 55k goes directly to the Backlog. In case that is over the Product Manager needs to create a Release Press and take it to Board Evaluation.
This Release Press needs to contain all the description, objectives, cost and benefits as well as KPI’s how will be validated.
User Stories solution design
Commits to what it feels it can accomplish
Investigation (new solutions, new approaches, new technologies, etc.)
Development (Code)
Development (Automated Tests)
Data Model
Unit Tests
Code Reviews
Peer Reviews
Deploys
Support
Demonstrations
Commits to what it feels it can accomplish (as part of Scrum Team)
Test Design
Development (Automated Tests)
Manual Tests
Deploys
Deploys Testing
Support (as part of Scrum Team)
Demonstrations (as part of Scrum Team)
Delivery Teams use Scrum.
Support Teams use Kanban.
By analogy with the "Definition of Done", the team makes explicit and visible the criteria (generally based on the INVEST matrix) that a user story must meet prior to being accepted into the upcoming iteration.
On a feature level, the acceptance criteria should be agreed up front BEFORE code is written.
The team agrees on, and displays prominently somewhere in the team room, a list of criteria which must be met before a product increment "often a user story" is considered "done".
On a feature level, the acceptance criteria should be agreed up front BEFORE the User Story is submitted to acceptance.