T-76.4115 Iteration T-76.4115 Iteration DemoDemoSoftware TrickeryPP Iteration

23.10.2007

2

AgendaAgenda

• Project status (10 - 15 min)– achieving the goals of the iteration– project metrics

• Work results (10 - 20 min)– presenting the iteration’s results

• Used work practices (5-10 min)

3

Introduction to the projectIntroduction to the project

• Party management system v2.0 (PMS)– Modular web-based system

• Tournament management system module (TMS)– Replaces existing system (non PMS-module)– Extension module for PMS– A solution for managing game tournaments– Main user groups

• Administrators• Tournament players• Outside spectators

4

Status of the iteration’s goalsStatus of the iteration’s goals

• Goal 1: Creating contacts to all relevant stakeholders – OK

• Goal 2: Understanding the problem domain fully – OK

• Goal 3: Creating a solution for the given problem – DISCARDED (Practically same as GOAL 2 at this point)

• Goal 4: Creating the needed architecture for the project to succeed– MOVED to beginning of I1 – Studied existing PMS architecture

• Goal 5: Learning the basic usage of needed technologies for the solution – OK

• Goal 6: High level schedule for the project – OK

• Goal 7: Identification and preparation for possible risks in I1 – OK

5

Status of the iteration’s Status of the iteration’s deliverablesdeliverables

• Project plan– OK, Except chapter 5.2 (QA Plan) which is to be delivered later (2.11.)

• Requirements document– OK, all important requirements documented in general level

• Progress report– OK

• SEPA diaries– OK

• High level Architecture– Moved to Iteration 1

6

Realization of the tasksRealization of the tasksStatus Realize

dPlanned Diff (Left

)Meetings OK 31 49,5 -18,5 0Creating iteration plan OK 12 12 0 0Requirements engineering OK 31 48 -17 0Project Plan OK 33 47 -15 0Studying existing system and technologies

Still Active

36 81 -45 45

Overview of system architecture Moved 0 15 -15 0Rest of PP tasks 41 30,5 +10,

5Total 184 283 -99 45

* unplanned task (= a new task added during the iteration)

7

Resource usageResource usage

• Individual studying didn’t realize as planned

• Architectural design moved to beginning of I1

• Estimating tasks without prior experience was hard

PM QM SA MaG

MiA ToA JaL MaH

ErH SUM

PP 52 91 45 20 15 15 15 15 15 283I1 45 49 60 85 55 65 65 65 65 544I2 53 50 45 85 55 70 70 70 70 558Total

150 190 150 190 125 150 150 150 150 1405

Original plan (in the beginning of the iteration)

Realization and updated plan (realized hours and updates)

PM

QM SA MaG

MiA

ToA

JaL MaH

ErH

SUM

PP 55 70 14 10 4 5 6 11 9 184

I1 42 60 75 95 60 70 69 69 71 611

I2 53 60 61 85 61 75 75 70 70 590

Total

150

190 150

190 125

150 150 150 150

1405

8

Resource usageResource usage

• Wed and Sun are control points

• Estimates upward• Tasks declared

done correct the curve

• Some members lazy about reporting hours during iteration -> Curve corrects itself during the end

PP-Iteration Burndown

0

50

100

150

200

250

W40, Sun W41, Wed W41, Sun W42, Wed W42, Sun W43, Wed

Time

Ho

urs

Rem

ain

ing

Actual Hours Remaining Reference Hours Remaining

9

Changes to the projectChanges to the project

• Major changes since the Iteration plan– Iterations split into two sprints– Developers will be divided into smaller team

10

RisksRisksID Risk P I E Effects Controlling actions R

1 Architecture delays whole project

7 9 63 No coding can be done since there is no architecture or the chosen architecture proves to be unusable for the project

Using incremental architecture techniques SA

2 Key members of customer's side do not have enough time to do their part in project

7 8 56 The project team will develop software with inadequate information and the end result will differ from what the customer really wants

Good planning beforehand meetings to utilize the time with the customer as efficiently as possible

PM, QM

3 Communication between project stakeholders fails

6 9 54 No one knows what is happening and stakeholders in the project become frustrated. Project suffers.

Communication practices well planned and applied according to the plan

PM

4 Quality of the product is insufficient

5 8 40 The product is poor to use and is unstable

See QA Plan for complete details. QM

5 Requirements are misunderstood

5 8 40 The product becomes something other than what the customer wanted

Quality manager presents requirements drafts to the customer frequently and makes sure everyone in project understands these requirements

QM

6 Project member quits in the middle of the project

4 9 36 Crucial information is lost and project scope must be decreased

Increase the amount of beer. Promote good team spirit, and discuss about possible problems openly. Developers should be teamed up to minimize the effect of losing one developer.

PM, SA

7 New technologies cause problems

5 7 35 Coding is slower than thought and resource estimations fail

Assigning coders to tasks that they have personal learning goals so that motivation of learning new is the highest possible

PM, SA

8 The project data is lost due to hard drive breakdown

1 10 10 All coding and documenting need to be done all over again

All data is stored in external environment provided by the customer. This environment is secured for such events. Also, each developer has his local copy of the repository.

PM

9 Member of SE-Trio is hit by a car or some other object

1 10 10 Crucial information is lost and project scope must be decreased

Decrease the amount of beer, SE-Experts must keep their replacements (assistants) in the loop to minimize the possible damage

PM, QM, SA

11

Results of the iterationResults of the iteration

• Project plan– Project Plan document

• Requirements – Requirements document

• SEPA diaries– Pyry Lahti and Markus Granström– Topic: Continuous Integration and Automated Testing

12

Project planProject plan

• Stakeholders and staffing• Project goals• Project practices • Tools

13

Stakeholders and staffingStakeholders and staffing

14

Project GoalsProject Goals

Goal Verification Criteria

1. All stakeholders are satisfied with the course outcome

All group members receive grade 4-5

2. Customer is satisfied with the product

Tournament management system can be used in both winter assembly and summer assembly

3. Project organization works smoothly

Everyone is still on speaking terms after the project

4. Everyone reaches their personal learning goals on this course

After the course each member has gained skill set which they defined

5. Winning the quality award with superior quality product

Group receives quality award from Accenture

6. Creating interest in the assembly organization among the group

One or more project team member becomes volunteer for ASSEMBLY Organizing

15

Project PracticesProject Practices• 1. Iterative development & Iteration planning

– 3 Iterations (PP, I1, I2)– 2 Sprints in each implementation iteration

16

Project PracticesProject Practices

• 2. Documenting– Documents created in the customer Wiki for easy availability– Weekly progress reports

• 3. Risk management– Identify, evaluate and prepare

• 4. Communication– E-mail & IRC– Mailing list– Meetings– Wiki for documents– Phone calls

• 5. Defect tracking and version control– Trac provided by the customer– Trac’s svn also used for time tracking (excel sheet)

17

Project PracticesProject Practices

• 6. Coding conventions– C#– PHP

• 7. Development & Quality practices– Continuous integration– TDD– Incremental rearchitecture– Peer testing– Developer days (Side-by-side programming)

18

Project toolsProject toolsTool Classification Version Availability Comment

MS Visual Studio .NET

Development 2005 Pro MSDN AA De facto IDE for C# in Windows

MonoDevelop Development 0.14 http://www.monodevelop.com Visual Studio "replacement" for Linux

Mono.net Development 1.2.5.1 http://www.mono-project.com/ .NET environment for non-Windows platforms

NAnt Development 0.85 http://nant.sourceforge.net/ A .NET build tool

NUnit Development 2.2 http://www.nunit.org/ A .NET unit-testing framework

AnkhSVN Development 1.0.2 http://ankhsvn.tigris.org/ Subversion-plugin for Visual Studio

TortoiseSVN Development 1.4.5 http://tortoisesvn.tigris.org/ Handy Subversion-client for Windows

Subversion Development 1.4.4 http://subversion.tigris.org/ The official command line SVN

CruiseControl.NET Development 1.3 http://pyppe.iki.fi:8880/ccnet/ Continuous Integration tool

Trac Development 0.10.3.1 https://kirves.assembly.org/trac/ Project Management and bug tracking

MS Office Documentation 2003 Installed on HUT Windows desktops Office for documenting

MS Visio Documentation 2007 MSDN AA Tool for making charts, and graphs

Doodle Communication - http://doodle.ch Tool for communicating availability

Google Calendar Communication - Link from http://.trickery.biz/ Calendar for project events

Irssi Communication - Installed on HUT computers Tool for general communication

TracWiki Communication 0.10.3.1 https://kirves.assembly.org/trac/pms/wiki/ Project wiki-page

19

Requirements EngineeringRequirements Engineering

• Conceptual model of TMS• Use case diagram• Overall status

20

Requirements Engineering: Requirements Engineering: Conceptual model of TMS (1/2)Conceptual model of TMS (1/2)

21

Requirements Engineering: Requirements Engineering: Conceptual model of TMS (2/2)Conceptual model of TMS (2/2)

22

Requirements Engineering: Use Requirements Engineering: Use case diagramcase diagram

23

Requirements Engineering: Requirements Engineering: Overall statusOverall status

• 8 use case descriptions• 18 functional requirements• 9 non-functional requirements

• Still needs to be officially approved

• All in all, requirements have been identified and represented quite well.– Good start for I1.

24

Experiences on work practicesExperiences on work practices• Time reporting is still troublesome

– Needs time specific DL (currently only Wed and Sun)

• Weekly meetings with customer– Seems to be a good way for sharing knowledge between stakeholders

• Individual studying – Needs benchmarking or tasks with deadlines

25

Any Questions ?Any Questions ?

• Thank you !