Christina Dulude

This is a session in the Technical: Propeller Hats Required Track at HighEdWeb, presented by C. Daniel Chase at the University of Colorado.

Principles behind the Agile Manifesto:

• Highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change.
• Deliver working software frequently, with a preference to the shorter timescale.

Business people must work together, rather than being isolated in silos. Also physical proximity and face-to-face communcation. Not keeping everyone in their own offices.

Agile processes promote sustainable development. Keeping sponsors, developers, users involved should be able to maintain a constance pace on the project. Agile methodologies include: Agile modeling, Extreme programming, Scrum.

Source code management: Version control, release tracking, development vs. production code lines.

Test driven development: What does this section of code do? Write a test first. Write code to pass the test

• Unit testing: Component level, which finds basic logic and syntax errors.
• Functional testing: Application level.

Continuous integration includes automated check-out, automated build, automated testing, immediate feedback for failures. Refactoring improves readability of code, but does not fix bugs or add new functionality. Test first.

Design patterns: Most problems have been solved before and solutions optimized. Using standard constructs make it easier to maintain code.