Please enable JavaScript.
Coggle requires JavaScript to display documents.
Agile Software (SCRUM (Sprint Planning (Tracking (Burnup (Total work, Work…
Agile Software
SCRUM
Roles
Product Owner
Scrum Master
Team
Rituals
Sprint Planning
Sprint Backlog
Daily Standup
Sprint Review
Sprint retrospective
Sprint Planning
Backlog grooming
Reassessment
Story selection
Sprint capacity
Sprint goal
Potential stories
Acquire confidence
Refine goals
Make commitment
Core Team
4 hours
Sprint 0
Setup
Tracking
Burndown
Work left
Burnup
Total work
Work completed
Task Board
To do
In Progress
Done
Daily Standup
Priorities
Limit WIP
Generalists
Discipline
3 questions
yesterday?
today?
roadblocks?
Be SHORT
Sprint review
Work done
Sprint summary
Demo
1-2 hours
Core team + stakeholders
Sprint retrospective
Process focus
NOT product
1 hour
Core team only
Continuous improvement
Action follow-up
Only a few
Fundamentals
Development
Cons
Requirements in advance
Misinterpretation
Tunnel Effects
Waterfall
Requirement
Architecture
Coding
Integration Test
UAT
Production
Agile
Mindset
Short Cycles
CI/CD
Models
Predictive
Defined
Adaptative
Incremental
Blocks
Iterative
All
Upgrades
Principles
Learning Cycle :check:
Collaboration
Values
Interactions
:warning: Processes
Working software
:warning: Documentation
Customer collaboration
:warning: Contract Negotiation :
Responding to change
:warning: Following a plan
Principles
Customer satisfaction
Welcome changes
Even late
Deliver frequently
Business & Dev
Daily Work
Motivated individuals
Face-To-Face
Working software
Simplicity
Mindset
Pros
Detect translation
Priority management
Project visibility
Team productivity
Cons
Architecture/DBA issues
Unpredictable
Customer participation
Not suitable
Predictive
Repetitive
Application
Small bite-size chunks
Function collaboration
Culture
Journey
Chartering
User needs
High level architecture
Release planning
Delivery
Repeat
Framework
SCRUM
70%
Kanban
XP
Lean Startup
User Stories & Requirements
Requirements
Card
Conversation
Confirmation
Adaptive
Just Enough
Documentation
User Stories
As a <role type>
I want to <perform task>
So that <achieve this goal>
Epic
Stories
Dev Stories
Acceptance tests
What
Not How
Spikes
Research
Knowledge gathering
Time-boxed
Definition of done
Good
Independent
Negotiable
Valuable
Testable
Estimable
Small
Generation
Writing workshop
Users
Personas creation
Stories alone
Gathering
Product Backlog
Estimated
Prioritized
Right details
Emergent
Story mapping
Timeline
User Activities
User Tasks
User Stories
Frame Problem
Map big picture
Explore
Slice out release
Co-ownership
Flexible
Estimation
Multi-Level
Just Enough
Adapt
Frequent
Release Planning
Sprint Planning
Daily Standups
Concepts
Effort
Work Days
Uninterrupted
Accuracy
Sizing buckets
Relative Vs Absolute
Story Points
Ideal Day Buckets
Styles
Card Sorting
Smallest & Largest
Buckets creation
Free Form
Planning Poker
Consensus
Engaging
Time consuming
Velocity
Work
1 Sprint
Skip
Anomalies
Release Planning
Fixed scope release
User Value
Learning Value
Risk mitigation
Dependencies
Nb Sprints
Fixed date release
Nb Points
Release Tracking
Burn Up
Cumulative completed
Story Board
Backlog
Development
Testing
Done
Cumulative flow diagram
Cycle Time
WIP
XP
eXtreme Programming
Social Change
Adaptative
Cons
Prescriptive
Scalability
Incremental Design
Pair Programming
Values
Simplicity
Only necessary
Communication
Work together
Courage
No hide
Feedbacks
Respect
Practices
Primary
Sit together
Whole team
No fractional
Informative workspace
15 seconds
Dynamic
Energized work
Pair programming
Stories
Estimate early
Weekly cycle
Slack
Buffer time
10 minutes Build
Continous Integration
TDD
Incremental Design
Refactor
Process
Release Planning
Iteration
Acceptance Tests