Part 2 of the Module

Learning to Craft Code is Challenging Every skill we have acquired was trick at first We need to take baby steps We need proper support

Agile Development Scrum Master Sprint Pair Programming Product Backlog SPRINT Backlog

Next Year May of you will take on a systems development project Team development Individual development (Or you will decide never to write code ever again!) The second half of this module is your play pen

Baby Steps Test Driven Development (Programming Pathways) Pair programming SCRUM Teams 14 day SPRINT – 3 x SPRINT Logs (assessed) These are the tools that will help you build skill and confidence

The system design Class diagram describes your code

Test Driven Development Provides the scaffolding that supports the structure

Interface Design Describes what the interface will do

Version Control

Avoiding Loss of Work Jane opens clsDataConnection in Visual Studio Bob adds a new method to clsDataConnection Bob saves his work on the class Jane completes her work modifying the code for clsAddressBook In the process Jane also saves clsDataConnection This reverts clsDataConnection back to its original version overwriting the new code created by Bob

Wider Implications for Customers Bob and Jane work on the system to produce version 1.0 of the product Version 1 is released to customers More work is carried out and version 1.1 is released which is chargeable Some customers report that with version 1.0 there is a bug Customers refuse to upgrade to version 1.1 due to the cost and want a fix for version 1.0 (This will create version 1.01) The question then arises how to manage the code not just to handle multiple versions of the code in use by developers but also multiple versions of the code over the history of the system. These problems are not trivial!

Communication and Organisation Team members must talk to each other Clear idea of who is doing what

This Week and Next Finish off claims for the first deliverable You may not make changes on that work 10 min per person Schedule A teams wk 16 Schedule B teams wk 17 Clear the deck so that we may focus on the development of the system