Agile Software Development Landscape

Get Started. It's Free
or sign up with your email address
Agile Software Development Landscape by Mind Map: Agile Software Development Landscape

1. Scaled Frameworks

1.1. SAFe

1.2. LeSS

1.3. DSDM

2. Frameworks

2.1. Scrum

2.1.1. Roles Intro Product Owner Role Focussed Training Certified Training ScrumMaster Role Focused Training What does a ScrumMaster do? Certified Training Development Team

2.1.2. Events Sprint Plannng Sprint Daily Scrum Incentivising Attendance Sprint Review How to Retrospective Backlog Refinement

2.1.3. Artefacts Product Backlog Sprint Backlog Product Increment

2.1.4. Definition of Done

2.1.5. Training Materials Suitable For Newbies What BYOS Scrum Simulation with Lego

2.1.6. Resources Scrum Primer The Scrum Guide

2.1.7. Working Agreements

2.1.8. Values Focus Openness Commitment Courage Respect

2.2. XP

2.2.1. XP Game

2.2.2. Extreme Programming Explained : Kent Beck

2.2.3. Values Communication Simplicity Feedback Courage Respect Others

2.2.4. Principles Humanity Economics Mutual Benefit Self-Similarity Improvement Diversity Reflection Flow Opportunity Redundancy Failure Quality Baby Steps Accepted Responsibility

2.2.5. Who New members of an XP team

2.2.6. Practices Primary Sit Together Whole Team Informative Workspace Energised Work Pair Programming Stories Weekly Cycle Quarterly Cycle Slack Ten-Minute Build Continuous Integration Test-First Programming Incremental Design Corollary Real Customer Involvement Incremental Deployment Team Continuity Shrinking Teams Root-Cause Analysis Shared Code Code and Tests Single Code Base Daily Deployment Negotiated Scope Contract Pay-Per-Use

2.3. Kanban

2.3.1. Kanban : David J. Anderson

2.3.2. Kanban Pizza Game

2.3.3. GetKanban Board Game

2.3.4. WIP

2.3.5. Values & Principles

2.3.6. Principle of flow

3. Practices

3.1. intro

3.2. What

3.2.1. Pair Programming

3.2.2. Common Code Ownership

3.2.3. Behaviour Driven Development (BDD) Bridging the Communication Gap by Gojko Adzic

3.2.4. Test Driven Development (TDD) intro

3.2.5. Refactoring Intro Refactoring: Improving the Design of Existing Code : Martin Fowler, Kent Beck et al

3.2.6. Continuous Delivery Continuous Delivery : Jez Hunble

3.2.7. Continuous Integration (CI)

3.2.8. Simple Design

3.2.9. Cross-functional teams

4. Lean

4.1. Lean Primer

5. Agile Requirements

5.1. Who

5.1.1. Product Owners

5.1.2. BA

5.1.3. QA

5.2. What

5.2.1. 3Cs

5.2.2. User Stories User Stories Applied by Mike Cohn

5.2.3. INVEST

5.2.4. Acceptance Tests

5.2.5. Splitting Stories

5.3. When

5.3.1. Before building backlogs

5.4. Duration

6. Learning Pathway

6.1. Agile Newbie

6.1.1. Intro to agile

6.2. ScrumMaster / Agile Coach

6.2.1. Responsibilities Ensuring adherence to the Scrum process Removal of impediments

6.2.2. What does a ScrumMaster do?

6.2.3. How do I work with the other Roles in Scrum?

6.3. Product Owner

6.3.1. Responsibilities ROI (scrum definition) Managing stakeholders Maintain the Product Backlog Determines 'what' needs to be done

6.3.2. How do I work with the other Roles in Scrum?

6.4. Developer / Development Team

6.4.1. Responsibilities Determines 'how' to deliver the desired functionality Creates the Sprint Backlog

6.4.2. How do I work with the other Roles in Scrum?

6.4.3. Role Agile Team Member

7. Agile Planning

7.1. Relative Estimation

7.2. Agile Feature Estimation

7.3. Release Planning

7.4. Iteration Planning

7.5. Agile Estimating and Planning by Mike Cohn

8. Metrics

8.1. Velocity

8.2. Story Points

8.3. Burndowns

9. Manifesto

10. Start Here