Agile Approaches
Scrum Artifacts
Product Backlog Sprint Backlog Increments
Kanban Principles
- Start with current state - Agree to pursue incremental, evolutionary change - Respect the current process, roles, responsibilities & titles - Encourage acts of leadership at all levels in your organization
Lean Concepts
- eliminating waste - JIT production (small batch sizes) - focus on value/quality
Kanban Core Properties
- visualize workflow - limit WIP - manage flow - make process policies explicit - implement feedback loops - improve collaboratively
Scrum Team Members
1) Product Owner: responsible for maximizing value of the product 2) Development Team: cross-functional, self-organizing team who have everything they need within the team to deliver working product 3) Scrum Master: responsible for: - ensuring the Scrum process is upheld - ensuring the Scrum team adheres to practices & rules - coaches the team on removing impediments
Kanban method may be best used when a team or org is in need of the following conditions:
1. Flexibility - teams are not typically bound by timeboxes and work on highest priority item in backlog 2. Focus on continuous delivery - teams are focused on flowing work through the system to completion and not beginning new work until WIP is completed 3. Increased productivity & quality - productivity & quality are increased by limiting WIP 4. Increased Efficiency - removing non-value-added activities 5. Team Member Focus - by limiting WIP 6. Variability in the workload 7. Reduction of waste - transparency makes waste visible to be removed
XP Key Principles
1. Humanity 2. Economics 3. Mutual Benefit 4. Self-Similarity 5. Improvement 6. Diversity 7. Reflection 8. Flow 9. Opportunity 10. Redundancy 11. Failure 12. Quality 13. Baby Steps 14. Accepted Responsibility
Crystal Clear
?
Crystal Orange
?
Crystal Red
?
Crystal Yellow
?
Kanban Board
A visualization tool and information radiator that enables improvements to the flow of work by making bottlenecks and work quantities visible. low-tech, high-touch technology provides clear insight to: - workflow - bottlenecks - blockers - overall status
Scrum
An agile framework for developing and sustaining complex products, with specific roles, events, and artifacts. - a single-team process framework used to manage product development - uses an iterative approach to deliver working product - run on timeboxes of one month or less with consistent durations called sprints where a potentially releasable product is produced
Kanban Method
An agile method inspired by the original Kanban inventory control system and used specifically for knowledge work. allows for a continuous flow of work and value to the customer by pulling single items through the process continuously and limiting work in progress to optimize flow (uses a pull system to move the work through the process) a holistic framework for incremental, evolutionary process and systems change for orgs. the original 'start where you are' method - less disruptive to begin implementing - less prescriptive than other agile methods does NOT use timeboxed iterations more important to complete the work than it is to start new work
Extreme Programming (XP)
An agile software development method that leads to higher quality software, a greater responsiveness to changing customer requirements, and more frequent releases in shorter cycles. - holistic set of practices intended to improve the results of software projects
XP Core Values
CSRFC 1. Simplicity 2. Communication 3. Feedback 4. Courage 5. Respect
Scaled Approaches
Crystal Methods Scrum of Scrums Lean Large Scale Scrum (LeSS) Disciplined Agile (DA) Scaled Agile Framework (SAFe)
Which agile approach is based on the philosophy of distilling a given best practice to its purest, simplest form and applying that practice continuously throughout the project?
Extreme Programming
Crystal Common Properties
Frequent delivery Reflective improvement Close or osmotic communication Personal safety Focus Easy access to expert users Technical environment with automated tests, configuration management, and frequent integration *the more properties there are in a project, the more likely it is to succeed
XP Practice Areas & 12 Primary Practices
Organizational - Sit together - Whole team - Informative workspace Technical - Pair programming - Test first programming - Incremental design Planning - user stories - weekly cycle - quarterly cycle - slack Integration - 10-minute build - continuous integration - test-first
Crystal Core Values
People Interaction Community Skills Talents Communications
Agile approaches are split into what two categories?
Scaled Approach Team Method
What is the most common Agile approach?
Scrum
Team Methods
Scrum Kanban eXtreme Programming (XP) Feature-Driven Development (FDD) Agile Unified Process (AgileUP) Dynamic Systems Development Method (DSDM)
Crystal Methods
designed to scale and provide a selection of methodology rigor based on project size (# of people involved in the project) and the criticality of the project uses different colors based on weight to determine which methodology to use comes from the word gemstone where the various faces represent the underlying core principles and values
Agile and Kanban are both subsets of
lean
Scrum events
sprint sprint planning daily scrum sprint review sprint retrospective