In this course participants will gain an understanding of the agile mindset, practices and structure needed for their success as the dedicated technology team that enables technology solutions in an agile delivery methodology for the Product.
By successfully completing the Agile Delivery essentials course, participants will understand core foundational concepts of agile, the roles & responsibilities of the delivery team, the different product teams and methodologies, and how to successfully deliver in an agile framework.
Mindset, Funding, Org Structure
Mindset, System, Practices
System, Resourcing, Funding
Resourcing, Funding, Tooling
Focusing on things the team has no power to change
Not having a retrospective because the team is too healthy or busy
Product Delivery Manager leading the Retrospective
Not leaving the Retrospective with action items
Something a customer is able to purchase
A good or service that offers value to a customer
An application or software
All of the above are products
Creates a daily plan for the team
Holds people accountable for their work
Gives others insight on what I worked on yesterday
Allows for time to bring up roadblocks that need to be addressed
Number of days for a team to execute a sprint / number of days to release
Number of minutes that should be spent on each work item / number of hours that should be spent on each sprint
Number of support items that should be planned for in a sprint / number of strategy items that should be planned for in a sprint
Number of days to make or break a habit / number of days for something to become a part of your lifestyle
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Following a plan over responding to change
Customer collaboration over contract negotiation
Sprint Financial Planning
Backlog Refinement
Sprint Planning
Daily Stand-ups
Tasking is done by the team and for the benefit of the team
Tasking helps provide clarity around the implementation strategy for each story
Tasks are mandatory for all stories
Tasks can be used to develop new skills
Planning is based on tasks rather than stories
Commitment is unrealistic or no commitment is reached
No time is reserved for support activities
All of the above are common anti-patterns
Traditional Project Team
Enabling Product Team
Platform Product Team
Project Team
2 weeks or less
3 weeks or less
A month or less
However long is needed/committed to
What I worked on yesterday
What I completed yesterday
What I will complete today
What is stopping me from completing my work
Showcasing working software
Showcasing a slide deck of what the new functionality will look like
Showcasing product financials and budget
Showcasing product roadmap, release plan, and burn up chart
Forming
Norming
Maturing
Storming
WIP limits help drive predictable teams
WIP limits help understand the speed of the product team
WIP limits gives teams the ability to put work on hold
All of the above
Each story is delivered as a piece of working software
Working in small, valuable pieces allows for constant feedback
Encourages collaborative effort from the entire team, not just individual work
Allows to financially plan in small time frames, lowering cost
They provide agile coaching to the product team
They manage sprint work for the product team
They determine what will be in each sprint
They are able to serve as an interim resource manager for the product team
Additional criteria that was not addressed in the previous sprint
What high level criteria will be needed in the sprint
Criteria that must be true before work can start
A list of requirements that depicts the entire customer experience of the product
A list of requirements needed
A requirement that depicts the specific capability needed
A list of proposed technical solutions
A lists of requirements that depicts the entire customer experience
The speed or rate the product team progresses through a sprint
How quickly product team members can execute work
How quickly stakeholders can expect demand to be delivered
The quality of development over time
The rise or drop in bugs within the product
Financial consumption over time
Percentage of the project complete
User stories completed from the backlog over time
Coordination with the Scrum Master
Time tracking through work items
Rely on sprint planning and what is committed
Teams are fully dedicated to the Product
Developer
Scrum Master
Product Owner
Product Delivery Manager
Allows for better planning
Accounts for team members availability
Drives quicker velocity
Allows to gradually increase the sprint backlog each sprint
Product Owner
Scrum Master
Product Delivery Manager
Product Team
Helps drive conversation with the product team
Allows the Product Team to understand how users will interact with the product
Provides the Product Team with a step-by-step solution
Helps reduce the likelihood of guessing
Gives the ability to change quicker
Reduces risk
Provides greater visibility
Development takes less time
Epic, Feature, User Story, Task
Feature, User Story, Epic, Task
Theme, Feature, Epic, User Story
Feature, Theme, Task, User Story
Allows the product team to pull out and add in to shift priority during sprints
Ensures the product team is working on the highest priority items during sprints
Gives the product owner the ability to rearrange work items based on priority in real time
Non of the above
The amount of work items the team commits to in a sprint
The average amount of work the team is able to do in a sprint
The number of work items completed in a given time period
The estimate of how many hours it will take to complete an Epic
Product Owner
Product Team
Product Delivery Manager
Scrum Master
True
False
Product Team
Product Delivery Manager
Product Owner
Product Stakeholders
Monthly
Quarterly
The end of every sprint
The completion of an Epic
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.