Post-Agile Checklist<br />What to do after getting Agile in place<br />
Source Control<br />Unit Tests<br />Automated Builds<br />Continuous Delivery<br />What To Look At<br />
Don’t have it?<br />Collaborate between developers<br />Important even in single person teams<br />How did your code chang...
Don’t have it?<br />Does that new feature work?<br />Did you break anything else?<br />Did you really fix the bug?<br />Wi...
Don’t have it?<br />Take out the manual steps.<br />Does everything compile?<br />Already have it?<br />Do you have a cons...
Don’t have it?<br />Do you remember to run the tests?<br />Can you easily tell when the build broke?<br />Already have it?...
Fix broken windows<br />Remove impediments<br />Increase productivity<br />Remove manual steps<br />Does the entire team k...
Web/Blogwww.jesse-anderson.com<br />E-Mailjesse@jesse-anderson.com<br />More information<br />
Upcoming SlideShare
Loading in...5
×

Post Agile Checklist

6,145
-1

Published on

You have put a lot of time and effort into implementing Agile Software Development methodology in your team or company. But are you using Agile to its fullest extent and making the best use of it? In this presentation, I go over things which teams may forget about using or if they are already using them, I go over the in which it could work better.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
6,145
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Post Agile Checklist

  1. 1. Post-Agile Checklist<br />What to do after getting Agile in place<br />
  2. 2. Source Control<br />Unit Tests<br />Automated Builds<br />Continuous Delivery<br />What To Look At<br />
  3. 3. Don’t have it?<br />Collaborate between developers<br />Important even in single person teams<br />How did your code change?<br />Already have it?<br />Are you using it correctly?<br />Source Control<br />
  4. 4. Don’t have it?<br />Does that new feature work?<br />Did you break anything else?<br />Did you really fix the bug?<br />Will it break again?<br />Already have it?<br />Is code exercised thoroughly (positive/negative)?<br />OT: Code coverage<br />Are code paths “real world”?<br />Other automated testing<br />Unit Tests<br />
  5. 5. Don’t have it?<br />Take out the manual steps.<br />Does everything compile?<br />Already have it?<br />Do you have a consumable output like an installer?<br />Automated Builds<br />
  6. 6. Don’t have it?<br />Do you remember to run the tests?<br />Can you easily tell when the build broke?<br />Already have it?<br />Can you do a deploy with a single click?<br />Can you easily promote a build?<br />Do you have easy access to previous build artifacts?<br />Continuous Delivery<br />
  7. 7. Fix broken windows<br />Remove impediments<br />Increase productivity<br />Remove manual steps<br />Does the entire team know how to use the tools?<br />Summary<br />
  8. 8. Web/Blogwww.jesse-anderson.com<br />E-Mailjesse@jesse-anderson.com<br />More information<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×