Please enable JavaScript.
Coggle requires JavaScript to display documents.
AGILE - Coggle Diagram
AGILE
12 Agile Principles
Highest priority= satisfy the customer
early and continuous deliverable of valuable software
Welcome changing requirements
for customer's competitive advantage
Deliver working software frequently
Business and Software together
Projects around motivated individuals
environment
support
trust
Development Team face to face conversation
Working software
Sustainable development
Constant pace indefinitely
Sponsors
Developers
Users
Enhancing agility
Continuous attention to technical excellence
Good design
Simplicity
The art of maximizing the amount of work not done
Self organizing teams
The best architectures
The best requirements
The best designs
Regular intervals
How to become more effective
Tuning and adjusting behavior
Roadmap to Value
Stage 1: Product Vision
Goals for product
Alignment with company starategy
Owner: PO
Frequency: Annually at least
outer boundary of the product
Who and why will use the product
Product's differences than the competition
Stage 2: Product Roadmap
Product features
Owner: PO
Frequency: At least biannually
High level
Product Requirements
Prioritizing
General timeframe
Genral context
tangible features
Stage 3: Release Planning
Timing for release
Owner: PO
Frequency: At least quarterly
High level timetable
at the beginning of each release
Stage 4: Sprint Planning
Spesific iteration
Owner: PO and Development Team
At the start of each sprint
Scrum team
determines a sprint goal
outlines how to complete them
Stage 5: Daily Scrum
Coordination
Development Team
Daily
Stage 6: Sprint Review
Demonstration of working product
PO and Dev.
At the end of each sprint
Stage 7: Sprint Retrospective
Refinement
Scrum Team
At the end of each sprint
Development Events
Product Planning
Product Vision Statement
Product Roadmap
Release Planning
Sprint
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Artifacts
Product Vision Statement
Inspirational
Quick summary
What is the product?
How it supports company's strategies
Product Roadmap
High level initial view
of Product Backlog
identifies
gaps
Feature affinities
enables
Funding community
Product Backlog
to do list
ordered by priority
Release Plan
high level time table
outside the scrum
improves scrum success
Sprint Backlog
The goal
User stories
Tasks
Increment
Demostrated
working product
Agile Manifesto
Teams
Long living
Self organized
Small
Effective communication
Continuosly releasable product
Flexibility
Value
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Roles
Product Owner
Bridge
Work with Dev
Daily
To clarify requirements
Development Team
Create product
Analysts
Testers
Designers
Writers
Engineers
Editors
Scrum Master
Supporting Dev
Clearing roadblocks
Embrace and enable agile
Influence change informally
Stakeholders
Nol ultimately responsible of the product
Provide input
Regular feedback and support
To Dev
To PO
Agile Mentor or Coach
Outside the Scrum Team
Focuses on
Scope Flexibility
Team Input
Continuous Improvement
Essential Valuable outcomes
Building in quality upfront
Extreme Programming
Eliminating wastes
Lean
As a framework for exposing progress
Scrum