This document discusses how to eliminate waste and create value using Agile practices. It identifies sources of waste such as extra features, inventory, extra processes, handoffs, waiting, task switching, and defects. It recommends practices for eliminating waste like continuous prioritization, estimating only current features, value stream mapping, collaboration, 1-4 week iterations, daily standups, test-driven development, automation, and continuous improvement. The goal is to deliver high quality software in a timely manner while spending resources efficiently and fostering innovation.

1. Eliminate Waste and Create Value
using Agile Practices
by Nanda Lankalapalli

2. Value
Create More
Eliminate Value
Waste

3. Extra Features
Inventory
Extra Processes
Handoffs
Waiting
Task Switching
Defects

4. Extra
Features About 60% of the
features are RARELY or
NEVER used.
Build today’s priorities.
Continuous
Time to Market.
Prioritization
Put nice-to-have
features at the end of
the stack.

5. Inventory Do everything Just-in-
time
Unused features.
Estimate stories in
Detailed story points
requirements for
all the features.
Elaborate
requirements for the
Anything not current features
being used.
Plan only current
features

6. Extra
Processes
Identify and
Eliminate steps
not adding value.
Code directly
from the Story.
Value Stream
Mapping
Collaborate with
customer.

7. Handoffs
Team works directly
with customer.
Developers and
Testers are on the
same team. Collaboration
Most of the activities
are done as a team.

8. Waiting
Customer waiting
to see the product. 1 – 4 Week
iterations
Testers waiting for
the code to test.
Deliver often and
quick to testers
Waiting for
Impediments to be
resolved. Daily Standups

9. Task
Switching
Task switching
delays all tasks.
Keep resources
on the same
There will be project until done
overhead while
switching tasks.
Avoid
Less productive. multitasking

10. Test Driven
Defects Development
Test First.
Automated Unit Tests
Test Small.
Test Automation
Test Often.
Continuous
Integration

11. High Quality
Deliver Timely
Spend Right
Innovation
Continuous Improvement

12. Test Driven Development
High Automation
Quality Quality should
be backed in. Simple Design
Refactoring
-ilities of
Software. Pair Programming
Self Directed Team
Best solution.

13. Deliver
Timely Value delivered Value based
early. prioritization
Gains competitive Delay commitment
advantage.
Adaptive to
market conditions.

14. Spend
Right Eliminating waste
Eliminate waste
saves money.
Invest in people
Use saved money
for improvement. Invest in automation

15. Innovation
Have people with right
attitude
Foster innovation.
Empower the team to
Skills are important, make decisions
Attitude is more
important.
Have sustainable pace

16. Continuous Iteration retrospective
Improvement
Iteration review with
the customer
Inspect and Adapt.

17. Documentatio
Document the vision that
n doesn’t change
Do just enough
documentation. Add comments to executable
tests
Tests and Code speak. Have system metaphor. Make
code readable.
Use technology. Use digital pictures of white
boards and meetings video
taped.

18. Metrics Velocity
What’s left is more Iteration Burndown
important than what’s
done.
Release Burndown
Collect few important
metrics.
Other metrics as
needed

19. Nanda Lankalapalli
Nanda Lankalapalli
- Software Craftsman
- Agile Trainer and Coach
- Certified Scrum Master
- Certified Scrum Practitioner
THANK YOU