Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Agile And Scrum by Mind Map: Agile And Scrum
4.9 stars - 70 reviews range from 0 to 5

Agile And Scrum

7 Key Principles of Lean Software Development

Fundamentals

Agile and Lean Values and Principles

Agile Manifesto, Manifesto, 12 Principles of Agile Software

Declaration of Interdependency (DOI)

Use physical boards in small teams

Tool Support

Use electronical tools in large and distributed projects, Pivotal Tracker, Target Process, Jira / Greenhopper, Version One, Rally, etc.., Rational Team Concert

Self-Organisation

Agile Specification

Single Product Owner for Development Team

Structure Complex Products by Themes

Determine Business Value on Themes and Epics

Prioritize Backlog

Breakdown High Priority User Stories

Estimate High Priority User Stories

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

Specify Non Functional Requirements to minimize technical debt

New node

Continuous Learning / Improvement (Kaizen)

Retrospectives

Retrospect in short cycles (4-6 Weeks)

Inspect Development Process and Deliverables

Focus on identifying 3 action items for next development period

Control if last action items have been implemented

Ask team if time is well invested, Method: ROTI

Vary methods of investigation

Process Improvement

Balancing idealism and pragmatism

Use WIP-Limits to identify process weaknesses

Peer work

Pursue peer design

Pursue peer programming

Pursue peer reviews

Integrated Quality

Maintain Integrity

Specify and control Non-Functional Requirements

Performance Tests

Code Reviews

Perform Regression-Tests

Continuous Integration and Staging

Continuous Refactoring

Run code inspections and peer reviews

Use collective code ownership

High-Performance Teams

Team norming

Build Cross-Functional Teams

Limit Teams to 7 (+-2) Persons

Evolve Team Rules

Set Purpose of the Team

Stand-up Communication

Faciliate Communication between Team Members

Focus on Impediments and Team Issues

ScrumMaster is responsible for effectivness

Work environment

Give team members space to learn

Mentor new Team Members

Waste Aversion

Avoid or prepare Meetings

Keep Managers away from development team

Avoid Task Switching

Assign People to single Projects

Use WIP-Limits

Avoid and/or remove "Low Priority" Features

Avoid "unready" work

Avoid Bottlenecks and Delays in development process

Keep things as simple as possible

Remove unnecessary processes

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

Deliver Fast

tbd

Manage Complexity

Breakdown work into small concrete deliverables

Split projects into smaller releases with high customer value

Split schedule into small iterations as team syncpoints

Split your organisation and large projects into small cross functional teams

Strive for Technical Excellence

Avoid technical debt and maintain non-functional requirements

Use continuous integration and continuous staging to avoid late integration failures

Use test driven development to enable regression tests

New idea for SCRUM

yes