Agile Development Practices - Productivity
Download as PPTX, PDF1 like625 views
The document outlines key agile development practices emphasizing values such as individuals and interactions, working software, and customer collaboration. It introduces various methodologies under 'big A' and 'little a' agile, highlighting the importance of adaptability and regular process reviews. Additionally, it covers coding principles, clean coding practices, and effective use of Git for project management and productivity enhancement.
Agile Development Practices - Productivity
- 2. Traditional Big „A‟ Agile Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 3. Traditional Big „A‟ Agile Agile Modeling Agile Unified Process (AUP) Dynamic Systems Development Method (DSDM) Essential Unified Process (EssUP) Extreme Programming (XP) Feature Driven Development (FDD) Open Unified Process (OpenUP) Scrum Velocity tracking
- 6. Little „a‟ agile 1. Can you react immediately and without panic if external constraints on your project change? 2. Do you review your process frequently and regularly to make sure the answer to the first question is always yes?
- 7. How can we do this in waterfall or constrained environments?
- 8. Subterfuge!
- 9. Agile Coding
- 10. SOLID Coding Single Responsibility Principle Open/closed Principle Liskov substitution principle Interface segregation principle Dependency inversion principle
- 12. Clean Coding PIE Baby steps KISS YAGNI DRY BoyScout Rule Good Neighbor Rule
- 13. Using GIT for Great Good!
- 14. What Git is about 1. Use CVS as an example of what NOT to do. 2. Support a distributed workflow 3. Strong safeguards against corruption, PEBKAC or malicious 4. High Performance
- 16. Branching, Merging git branch NewBranch git checkout NewBranch <do work> git commit –a –m „bug fix‟ git checkout master git merge NewBranch
- 18. Git-tfs Treats TFS as a remote repository 1. Setup TFS “remote repository” 2. <do work> 3. Fetch latest 4. Merge 5. Use Checkintool.
- 20. Keep you hands where I can see them!
- 23. ReSharper
- 24. Beyond Compare
- 25. Notepad++
- 26. Resources
Editor's Notes
- #4: Short List from Wikipedia: http://en.wikipedia.org/wiki/Agile_software_development#Agile_methods
- #5: Photo fromhttp://www.flickr.com/photos/dnorman/2172773143/Creative Commons Attribution-NonCommercial 2.0 Generic (CC BY-NC 2.0)
- #9: Horse: http://www.flickr.com/photos/cristic/265149677/ CC Attribution 2.0 Generic (CC BY 2.0)Bunny: http://squeak.preeminent.org/orgBlog/C244531379/E20051003220643/Media/trojanBunny.jpg Fair Use
- #11: http://lostechies.com/wp-content/uploads/2011/03/pablos_solid_ebook.pdfSingle responsibility principlethe notion that an object should have only a single responsibility.Open/closed principlethe notion that “software entities … should be open for extension, but closed for modification”.Liskov substitution principlethe notion that “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”. See also design by contract.Interface segregation principlethe notion that “many client specific interfaces are better than one general purpose interface.”Dependency inversion principlethe notion that one should “Depend upon Abstractions. Do not depend upon concretions.”Dependency injection is one method of following this principle.
- #13: PIE – Program Intently and ExpressivelyBaby Steps – Don’t try to do the whole thing in once giant leap, cut off small pieces, work on them, test them, rinse, repeat. Keep this cycle tight so you know exactly when/where you messed something up.KISS – Don’t build a space shuttle, a bottle rocket would probably do.YAGNI – THROW AWAY CODE IF ITS COMMENTED OUT OR NOT IN USEDRY – Smack yourself if you copy paste code more than once. Move to method is great here, start with procedural then move to more genericized code.Boy Scout Rule – Leave it cleaner than you found it – renaming variables helps muchoGood Neighbor Rule – Cut your grass, make tests, automate things so you don’t leave a mess for your coworkers.
- #15: http://en.wikipedia.org/wiki/Git_(software)
- #18: Explain story with flaky VPN.Don’t have to be connected to the server to branch, merge, swap changes with coworkers.http://nvie.com/posts/a-successful-git-branching-model/- creative commons
- #19: Two-way bridge between GIT and TFS.
- #21: http://www.flickr.com/photos/tuxophil/54865095/sizes/l/in/photostream/
- #22: Original:http://en.wikipedia.org/wiki/File:AT4_rocket_launcher.jpg
- #23: http://www.geograph.org.uk/photo/1730107 -- CC Sharealike
- #25: http://www.flickr.com/photos/thebusybrain/2492945625/