Agile And Scrum

Critical Success Factors in Scrum an Lean Management

Get Started. It's Free
or sign up with your email address
Rocket clouds
Agile And Scrum by Mind Map: Agile And Scrum

1. 7 Key Principles of Lean Software Development

2. Fundamentals

2.1. Agile and Lean Values and Principles

2.1.1. Agile Manifesto

2.1.1.1. Manifesto

2.1.1.2. 12 Principles of Agile Software

2.1.2. Declaration of Interdependency (DOI)

2.1.3. Use physical boards in small teams

2.2. Tool Support

2.2.1. Use electronical tools in large and distributed projects

2.2.1.1. Pivotal Tracker

2.2.1.2. Target Process

2.2.1.3. Jira / Greenhopper

2.2.1.4. Version One

2.2.1.5. Rally

2.2.1.6. etc..

2.2.1.7. Rational Team Concert

2.3. Self-Organisation

3. Agile Specification

3.1. Single Product Owner for Development Team

3.2. Structure Complex Products by Themes

3.3. Determine Business Value on Themes and Epics

3.4. Prioritize Backlog

3.5. Breakdown High Priority User Stories

3.6. Estimate High Priority User Stories

3.7. Specify Aceptance Criteria of User Stories if PO is not full time available

3.8. Specify Non Functional Requirements to minimize technical debt

3.9. New node

4. Continuous Learning / Improvement (Kaizen)

4.1. Retrospectives

4.1.1. Retrospect in short cycles (4-6 Weeks)

4.1.2. Inspect Development Process and Deliverables

4.1.3. Focus on identifying 3 action items for next development period

4.1.4. Control if last action items have been implemented

4.1.5. Ask team if time is well invested

4.1.5.1. Method: ROTI

4.1.6. Vary methods of investigation

4.2. Process Improvement

4.2.1. Balancing idealism and pragmatism

4.2.2. Use WIP-Limits to identify process weaknesses

4.3. Peer work

4.3.1. Pursue peer design

4.3.2. Pursue peer programming

4.3.3. Pursue peer reviews

5. Integrated Quality

5.1. Maintain Integrity

5.2. Specify and control Non-Functional Requirements

5.2.1. Performance Tests

5.2.2. Code Reviews

5.3. Perform Regression-Tests

5.4. Continuous Integration and Staging

5.5. Continuous Refactoring

5.6. Run code inspections and peer reviews

5.7. Use collective code ownership

6. High-Performance Teams

6.1. Team norming

6.1.1. Build Cross-Functional Teams

6.1.2. Limit Teams to 7 (+-2) Persons

6.1.3. Evolve Team Rules

6.1.4. Set Purpose of the Team

6.2. Stand-up Communication

6.2.1. Faciliate Communication between Team Members

6.2.2. Focus on Impediments and Team Issues

6.2.3. ScrumMaster is responsible for effectivness

6.3. Work environment

6.3.1. Give team members space to learn

6.4. Mentor new Team Members

7. Waste Aversion

7.1. Avoid or prepare Meetings

7.2. Keep Managers away from development team

7.3. Avoid Task Switching

7.3.1. Assign People to single Projects

7.3.2. Use WIP-Limits

7.4. Avoid and/or remove "Low Priority" Features

7.5. Avoid "unready" work

7.6. Avoid Bottlenecks and Delays in development process

7.7. Keep things as simple as possible

7.8. Remove unnecessary processes

8. Huhu!!!! Was'n das hier???

9. Deliver Fast

9.1. tbd

10. Manage Complexity

10.1. Breakdown work into small concrete deliverables

10.2. Split projects into smaller releases with high customer value

10.3. Split schedule into small iterations as team syncpoints

10.4. Split your organisation and large projects into small cross functional teams

11. Strive for Technical Excellence

11.1. Avoid technical debt and maintain non-functional requirements

11.2. Use continuous integration and continuous staging to avoid late integration failures

11.3. Use test driven development to enable regression tests

12. New idea for SCRUM

12.1. yes