Agile Flashcards
Scrum pillars
- transparency
- inspection
- adaptation
Scrum values
- commitment
- focus
- openness
- respect
- courage
Developers
committed to creating any aspect of a usable Increment
Developers accountable for
- Creating a plan for the Sprint, the Sprint Backlog;
- Instilling quality by adhering to a Definition of Done;
- Adapting their plan each day toward the Sprint Goal; and,
- Holding each other accountable as professionals.
Product owner accountable for
- maximizing the value of the product
- backlog management
Backlog management includes
● Developing and explicitly communicating the Product Goal;
● Creating and clearly communicating Product Backlog items;
● Ordering Product Backlog items; and,
● Ensuring that the Product Backlog is transparent, visible and understood.
Scrum Master is accountable for
- establishing Scrum as defined in the Scrum Guide
- the Scrum Team’s effectiveness
Scrum master serves the team by
● Coaching the team members in self-management and cross-functionality;
● Helping the Scrum Team focus on creating high-value Increments that meet the Definition of
Done;
● Causing the removal of impediments to the Scrum Team’s progress; and,
● Ensuring that all Scrum events take place and are positive, productive, and kept within the
timebox.
Scrum master serves the product owner
● Helping find techniques for effective Product Goal definition and Product Backlog management;
● Helping the Scrum Team understand the need for clear and concise Product Backlog items;
● Helping establish empirical product planning for a complex environment; and,
● Facilitating stakeholder collaboration as requested or needed.
Scrum master serves the organization
● Leading, training, and coaching the organization in its Scrum adoption;
● Planning and advising Scrum implementations within the organization;
● Helping employees and stakeholders understand and enact an empirical approach for complex
work; and,
● Removing barriers between stakeholders and Scrum Teams.
Definable work
clear procedures that gave proved successful on similiar projects in the past
more definable work is automated
High uncertainty work
high rates of change, complexity and risk => hard for systems with up front control and change request process
Agile manifesto
individuals and interactions over processes and tools
working software over comprehensive documentation
customer collaboration over contract neotiation
responding to change over following a plan
Agile approach
any kind of approach, technique, framework, method or practice that fulfulls the values and principles of the agile manifesto
Lean thinking
- focus on delivering value
- respect for people
- minimize waste
- transparent
- adapt to change
- continuous imporvement
iterative and incremental approaches
- reduce waste and rework
use
- very short feedback loops
- frequent adaptation of process
- reprioritization
- regularly updated plans
- frequent delivery
Types of lifecycles
- predictive
- iterative
- incremental
- agile