The document discusses a lazy developer's approach to agile development. It advocates for planning concept ideation at the start of a sprint to jump start development. It also recommends using feature crews to focus on depth-first development of features, and continuous integration to enable continuous delivery. Finally, it notes that while traditional waterfall approaches are not wrong, agile emphasizes high-level breath design followed by low-level feature-focused design and coding in sprints to enable efficient sprint delivery.

1. A lazy developer’s life
#DOTITUDE
@kosalanuwan
Kosala Nuwan Perera
software craftsman, solution designer, user experience
sprint
evangelist
kosalanuwan.tumblr.com
I’m Kosala Nuwan
blog
delivery alertbox.tumblr.com
A software craftsmanship column
blog
model

2. A lazy developer’s life
#DOTITUDE #agenda
Sprint
There is traditional way of doing things, and there’s agile way!
sprint Plan
Concept ideation to jump start a sprint?
Develop
delivery Feature crews to depth-first development.
Ship
Continuous integration to delivery!
model

3. A lazy developer’s life
#DOTITUDE #agileway
Traditional approach
There is nothing wrong with Waterfall!
sprint is Breath-first
Spec every feature, design every feature, code every feature, test
every feature.
not a 7 deadly sins of waste
Overproduction, Transportation, Motion, Waiting, Over
processing, Inventory, and Defects.
waterfall Agile et al
High level breath design first. Low level design and code feature
by feature.

4. Plan Develop Deliver

5. Plan Develop Deliver

6. Plan Develop Deliver

7. Plan Develop Deliver

8. Emphasis on Sprint Delivery
#DOTITUDE
@kosalanuwan
Kosala Nuwan Perera
software craftsman, solution designer, user experience
fun
evangelist
kosalanuwan.tumblr.com
I’m Kosala Nuwan
blog
with alertbox.tumblr.com
A software craftsmanship column
blog
agile!