learning to craft code is challenging every skill we have acquired was trick at first we need to...

Post on 18-Jan-2018

218 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

Scrum Development Scrum Master Sprint Pair Programming Product Backlog SPRINT Backlog

TRANSCRIPT

Learning to Craft Code is Challenging

Every skill we have acquired was trick at firstWe need to take baby stepsWe need proper support

Scrum DevelopmentScrum MasterSprintPair ProgrammingProduct BacklogSPRINT Backlog

Next YearMay of you will take on a systems

development projectTeam developmentIndividual development(Or you will decide never to write code ever

again!)The second half of this module is your play

pen

Baby StepsTest Driven Development (Programming Pathways)Pair programmingSCRUM MasterSCRUM Teams14 day SPRINT – 4 x SPRINT LogsProduct backlogSPRINT backlog

These are the tools that will help you build skill and confidence

The system design

Class diagram describes your code

Test Driven DevelopmentProvides the scaffolding that supports the

structure

Interface Design

Describes what the interface will do

Version Control

Avoiding Loss of WorkJane opens clsDataConnection in Visual StudioBob adds a new method to clsDataConnectionBob saves his work on the classJane completes her work modifying the code

for clsAddressBookIn the process Jane also saves

clsDataConnectionThis reverts clsDataConnection back to its

original version overwriting the new code created by Bob

Wider Implications for CustomersBob and Jane work on the system to produce version 1.0 of the

productVersion 1 is released to customersMore work is carried out and version 1.1 is released which is

chargeableSome customers report that with version 1.0 there is a bugCustomers 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!

The Desire Path

Communication and OrganisationSCRUM Master co-ordinates proceduresTeam members must talk to each otherClear idea of who is doing whatAt all times the customer is always right

This Week and NextFinish off claims for the first deliverableYou may not make changes on that work10 min per personSchedule A teams wk 16Schedule B teams wk 17Clear the deck so that we may focus on the

development of the system

top related