Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile

No description
by

Hithem Aly

on 10 October 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile

Agile
Agile (Pull)
TDD, CI, Refactoring, PP
Manifesto
Individuals and interactions over processes and tools
Working Software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan


1- Produce Value early
2- Welcome change
3- iterative Delivery
4- Daily Business collaboration
5-Trusted Motivated Team
6- face to face communication
7- Working software
8- Sustainable pace
9- Technical Excellence

10- Keep it simple
11- Self Organize
12- Reflect and Adjust
High Visibility, Information Radiators
Reflect Value and Priority
(Moscow)
Continuous involvement
of customer
SCRUM, Vision, Requirements, Priorities
SCRUM Master, Max ROI
foreseeable future
well defined requirement
M2: Daily SCRUM
M1: Sprint Planning,
Release Planning
●What was done yesterday?
●What will be done today?
●What blockers are there?
M3: Sprint Review
for shippable features
M4
XP
XP
XP Principle 1
XP Principle 2
XP Principle 2
XP Principle 3 (Feedback)
XP Principle 4 (Courage)
XP Principle 5 (Respect)
Technique (Fine Scale Feedback)
Technique (Shared Understanding)
Technique (Continuous process)
Technique: Programmer welfare
Principle 1 – Focus on the business need
P2 –Deliver on time
P3 –Collaborate
P4- Never compromise quality
P5- Build incrementally from firm foundations
P6- Develop Iteratively
P7 –Communicate continuously and clearly
P8 –Demonstrate control
PM-Envision
PM-Speculate
PM-Explore
PM-Adapt
PM-Close,
Release

p1- Eliminate waste
p2- Amplify Learning
p4- Deliver as fast as possible
p5- Build Integrity
p3- Decide as late as possible
p6- Empower Team
See the whole, Think Big Act Small, Fail fast, learn rapidly
Scrum
XP
Atern DSDM
Lean

Kanban, Limit WIP
OUP
- Construction,
Development
OUP- Transition
OUP
- Inception,
Planning
OUP
- elaboration,
Staging
Osmosis communication
Card,
Conversation,
Confirmation
Invest
Independent
Negotiable
Valuable
Estimable
Small
Testable
Story Type
Estimated Value Point
Story Point
Dependency
Acceptance test
related use stories (estimates, Release planning)
lower priority, too big
Release Planning
Iteration Planning
Sum (SP)
Release BurnDown
CFD Little Law
WIP Limit
Techniques
1- Brain Storming
2- Mute Mapping
What went well?
What could be better?
What did we learn?
What still puzzles us?
Estimation

1-Story points
Relative, non linear scale
2- Ideal time,
Perfect Engineering Days
Elapsed Time (Time on the clock) actual amount of time
How hard is it (complexity)
How much of it there is (effort involved)
How risky is it
benchmark, Multiple benchmark (T-shirt sizing)
3- value points
Technique
1- planning poker (< 20 Story)
Estimation technique
Wideband Delphi
Affinity Estimation (>=20 story)
T-Shirt Sizing
Agile Product Roadmap
Functional,
non functional
enhancements
Agile Project Charter
Vision
Mission
Success Criteria
Agile Personas
When, where, why
Job
Goals
Agile Modeling
Unit tests in TDD focus on building the code right (From Developer) ;
Acceptance Tests focus on building the right code (From Customer).
1-Discuss
2- Distill
3- Develop
4- Demo
ATDD
Value based Prioritization
business case: SWOT
Return on Investment
Net Present Value
Internal Rate of Return
Payback Period
Value calculation
By Product Team
Prioritization
Thresholds
Linear
Relative Weightings
w = Value/ cost * Risk
Minimum Marketable Feature
Revised Weekly
High Risk
Risk- I, A, R
Risk- Identify
Review
Risk- Identify
Risk- Identify
Risk - Review
Risk- Identify
Assess
Response
Risk- Assess
Risk- Respond
Risk- Identify
Assess
Response
Risk Management
Assess
Review
Risk- Spike
Exposure
Response
Metrics
BAC = price of SP * (Product backlog) (PSRP Planned Story Release Point)

PV =
Planned Percentage
* BAC
Planned Percentage
= Number of Sprints/
Total Number of Sprints planned
Total Number of Sprints planned
= Product backlog/ velocity (Baseline Velocity)

EV =
Actual Percentage
* BAC
Actual Percentage
= Story points completed / Total planned story points

EAC = BAC/CPI
ETC = (BAC-EV)/CPI, EAC- AC

CPI = EV/AC
SPI = EV/PV
Escaped Defects
Velocity
Measure outcomes, not outputs
Measure results, not activity
Measure work items done, not time spent per task
Follow trends, not numbers
Value Stream mapping
analyze the flow of information, people, and material required to bring a product or service to a consumer
Lean, identify and eliminate process waste and improve throughput.
Waste
1- Partially done work, 2-Extra processes
3- Extra features 4- Task switching
5- Waiting 6- Motion 7- Defects
spaghetti diagram
Product Box
Spider web
Buy a Feature
White Elephant Sizing
Sailboat
Learning Matrix
60 Min
Disaggregation
ROTI
Agile Road Map
Story Mapping
ROI
Unit
Component
Integration
Soft Skills
3 level of Listening
Whitworth

Kanban is not a task board (waterfall)
Set the Stage
Gather Data
Generate Insights
Decide What to Do Now
Close the Retrospective
Iteration, Release, Project, Surprise
Auto Build Report
Support tools for analysis
Product Manager, Iteration Manager, Developers, and Testers
Iterative,
feature-based,
time boxed,
and incremental

Iteration 0
Full transcript