1 / 18

Headspring Certified Training Agile Boot Camp for .Net

Headspring Certified Training Agile Boot Camp for .Net. Presented by Jeffrey Palermo CTO, Headspring Systems Microsoft MVP, MCSD.Net jpalermo@headspringsystems.com. About me. CTO, Headspring Systems Software management consultant Agile coach MCSD.Net Microsft MVP Certified ScrumMaster

lilka
Download Presentation

Headspring Certified Training Agile Boot Camp for .Net

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Headspring Certified TrainingAgile Boot Camp for .Net Presented by Jeffrey Palermo CTO, Headspring Systems Microsoft MVP, MCSD.Net jpalermo@headspringsystems.com

  2. About me • CTO, Headspring Systems • Software management consultant • Agile coach • MCSD.Net • Microsft MVP • Certified ScrumMaster • Director, Austin .Net User Group • Board member, AgileAustin • INETA speakers bureau • U.S. Army Veteran • Party with Palermo

  3. Agile, Lean & Extreme Programming

  4. 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

  5. Lean • Eliminate waste • Amplify learning • Decide as late as possible • Deliver as fast as possible • Empower the team • Build integrity in • See the whole

  6. Extreme Programming • Whole team • Planning game • Small releases • Customer tests • Simple design • Pair programming • Test-Driven Development • Design improvement • Continuous integration • Collective code ownership • Coding standard • Metaphor • Sustainable pace

  7. Source Control

  8. Repository structure -Trunk -Tags -Branches

  9. Automated build with nant

  10. What does a build do? • Compiles • Links • Versions • Packages • Runs all tests • Succeeds or fails, no gray area.

  11. Why automate? • Avoid manual steps • Performs steps the same every time • Save human time • Increase rate of feedback

  12. Prerequisites • Structured source control • Trunk • Tags • Branches • Access to all key dependencies within trunk working copy

  13. Build goal From a checkout of the trunk, run a single command and output a verified, versioned, packaged, and deployable software application.

  14. Key Steps • Increment version number • Create database that will be used in build testing • Compile and link all code files into .Net assemblies • Execute all primary tests to verify compiled software • Aggregate all files necessary for a deployment and package in organized .zip file • Commit deployable .zip to Subversion • Tag build with version number

  15. Domain-Driven Design

  16. Object-Relational Mapping

  17. Why ORM? • Save human time. • Consistent quality • Work in object-oriented manner rather than data-oriented.

  18. That’s all, folks!

More Related