The Delivery Team is responsible for creating the tasks from the features and stories. Work is done to complete the story and/or feature so that it meets the definition of done. The Delivery Team as a whole is responsible for collaborating to achieve these responsibilities.
The Product Specialist collaborates with the Product Line Team to continually mature the backlog and ensures the delivery team doesn't get blocked or surprised; researches questions on how the functionality is implemented; works closely with the delivery team to ensure stories are refined and available for sprint planning.
Why This Is Important:
A prioritized ready backlog is key to making and meeting commitments
Key Things That Need To Be Accomplished:
Write stories to support the Product Line Team, articulating what and why
Attend all ceremonies as a member of the team
Work with the Product Line Team to validate the priorities of the backlog
Ensure Stories have valid Acceptance Criteria and meet the Definition of Ready
Ensure that Story level testing effectively meets the quality needs of the product
Ensure with the Delivery Team that the stories are refined and ready for sprint planning
Accept or reject stories as having met Acceptance Criteria by the end of the sprint
Successful Execution Of The Role Results In:
Incremental value delivery and a greater shared understanding of what is needed and why
The Developer develops/configures software according to standards and designs defined by the architecture community; confirms that stories meet acceptance criteria by both validating the fit to need and verifying that the system performs as intended.
Develop/configure software according to standards and designs defined by the architecture community
Why this is important:
Backlogs are transformed into Working Tested Product, the foundational basis for measuring progress
Key things that need to be accomplished:
Define with the rest of their team how and when the stories can be delivered
Identify solutions and create options for the technical approach and design that are in alignment with the architecture strategy
Help refine upcoming stories and identify when spikes are needed to reduce risk
Estimate with the rest of the team stories in the backlog
Doing this successfully results in:
Creation of optionality in the solutions for the Product Line Team to maximize value
Ability to understand the team’s capacity to create working tested products on a regular cadence
Knowledge workers who can demonstrate mastery autonomously and with a shared sense of purpose
Confirm that stories meet acceptance criteria by both validating the fit to need and verifying that the system performs as intended
Why this is important:
Working Tested Product includes producing both a high-quality product and solving the needs of the users
Key things that need to be accomplished…
Stories completed in a timely manner and validated as meeting the acceptance criteria
Stories developed with a quality-first mindset of no net new defects
Automation is continuously increased, reducing the time to test
Doing this successfully results in:
Higher quality code is created much more consistently with less rework
Focus is placed on the value being produced vs completing items
The QA/Test Engineer creates and conducts automated or manual testing on the system and confirms that stories meet acceptance criteria by both validating the fit to need and verifying that the system performs as intended.
Why this is important:
Working Tested Product includes producing both a high-quality product and solving the needs of the users
Key things that need to be accomplished:
Define with the rest of their team how and when the stories can be delivered
Stories completed in a timely manner and validated as meeting the acceptance criteria
Stories developed with a quality-first mindset of no net new defects
Automation is continuously increased, reducing the time to test
Doing this successfully results in:
Higher-quality code is created much more consistently with less rework
Focus is placed on the value being produced vs. completing items
The Scrum Master ensures the day-to-day activities of the Delivery Team are happening and collaborates with Product Orchestrator.
Ensure the day-to-day activities of the Delivery Team are happening
Why this is important:
The business can’t make and meet commitments effectively unless the System of Delivery is running predictably
The team will be able to coordinate and orchestrate better with stakeholders and other teams
Key things that need to be accomplished:
Ensure that the Delivery Team is following the organizational guidelines of the activities for Scrum or Kanban
Ensure that the ALM tool/boards are being used effectively
Provide an escalation point for the team
Doing this successfully results in:
The team working more effectively
The team remaining in alignment with organization’s best practices
Collaborate with Product Orchestrator
Why this is important:
The team will be able to coordinate and orchestrate better with stakeholders and other teams
Key things that need to be accomplished:
Escalate to the Product Orchestrator when impediments arise that require their intervention to unblock
Doing this successfully results in:
Increased shared understanding of value and communication throughout the System of Delivery
