In our development, we don't treat every feature the same. An emergency bug may be treated differently from a normal feature request. Whereas an innovative new feature might require multiple iterations of user feedback. So why do we develop our process to treat every feature the same? NOTE: Yes, the slides mostly have only images. That is because the slides are from my talk from the meetup at Kanban Day, Chennai. I'm writing out the transcript for a LinkedIn article, and I'll post the link here once I'm done.

1. All features aren’t
equal
Siddharta Govindaraj

3. Is this
really
visualising
our actual
process?
Backlog Analysis Development Testing Done
…
…
… … … …
… … …
…
…
…

4. Design Development Review TestingNew Feature
UI Fix
Expedite
High Value
Investment
Analysis
Fix
Design
Options
Fix Release
Testing
Development Feedback Testing
Prototype Selection Development

6. UI Fixes
New Features

8. Expedite
High ValueNew Feature
Investment

9. What is the impact of having too
many expedite requests?

10. What if we have too many high
uncertainty items going on?

11. Should we balance risky features
with well known commodities?

12. Siddharta Govindaraj
https://www.linkedin.com/in/siddharta
Redd Angelo