T-76.4115 Sprint Demo

Team TarantinoIteration 1 / Sprint 2

12.12.2006

2

T-76.4115 Iteration demoT-76.4115 Iteration demo

Agenda

Project status (10 min) Achieving the goals of the sprint Project metrics Realized risks

Work results (15 min) MUPE status Wiki status

Used work practices (5 min)

Introduction

4

T-76.4115 Iteration demoT-76.4115 Iteration demo

Introduction to the project

Quentin primary goal is to agilize movie’s production stages.

It is a modern tools for collaboration.

Amount of information that is gathered during pre-production is huge

During production coherent information is vital since shots can be filmed in middle of nowhere. A simple misunderstanding can become very expensive!

Crew can get more tailored information

5

T-76.4115 Iteration demoT-76.4115 Iteration demo

Project plan: Development process

Iterative process Two development iterations, each divided into two sprints

Sprint contents Planning phase, overlaps with the previous sprint Development phase, features for this sprint are frozen Integration phase, the implemented features are verified

Sprint planning Features to be included are agreed with the customer at the start of the sprint Kick-off meetings with the whole team at the beginning of each sprint Reflection workshop at the end of each sprint, process improvement

Project PlanningIteration 1 Iteration 2

HolidaySprint 1 Sprint 2 Sprint 4Sprint 3

Colors:•Planning•Defeloping features•Integrating features

S1 S1 S1

S2

S3 S3

S4 S4 S4

S3

S2 S2

Project status

7

T-76.4115 Iteration demoT-76.4115 Iteration demo

Status of the S1s deliverables

The first version of the MUPE reader OK, still some problems when using with real device

The first version of the modified Wiki OK, some minor bugs to be fixed

Updated version of project plan and requirement document Not OK, formal versions of project plan and requirement document will be

produced only at the end of S2 QA Plan

OK Progress report

OK Test reports

OK

8

T-76.4115 Iteration demoT-76.4115 Iteration demo

Status of the S2’s deliverables

The first version of the MUPE-io OK

The second version of the modified Wiki Quite OK: Bold goals for S2 not fully realized, but technically challenging core

functionality in place. Updated version of project plan and requirement document

OK QA Plan

OK Progress report

OK SEPA diaries

OK? Test reports

OK

9

T-76.4115 Iteration demoT-76.4115 Iteration demo

Realization of tasks (S1)

202,320,8163434,333,836,527Total

75,258131619,8180,50DE

21,253,25000017,50,5QA

4,5002,51010IN

26,753,25073,7547,51,25LE

130024700TD

10000100RE

60,56,2536,55,753,751025,3PM

TotalRBTPLKJHTHTNJMActual

         

2794141,540413739,539Total

70,0016,0020,0012,0018,004,000,000,00DE

15,001,001,001,000,001,0011,000,00QA

4,000,000,500,000,001,002,500,00IN

88,0014,5014,5013,5013,5012,5011,508,00LE

12,000,000,003,004,005,000,000,00TD

11,004,000,000,000,003,000,004,00RE

79,005,505,5010,505,5010,5014,5027,00PM

TotalRBTPLKJHTHTNJMPlanned

10

T-76.4115 Iteration demoT-76.4115 Iteration demo

Realization of tasks (S2)

21432,84735,2545,51516,521,5Total

13226,53824,7538,34,500DE

9,5020006,51QA

243,7543,253,753,55,50,25LE

30000300TD

2,250000002,25RE

42,82,537,253,544,518PM

TotalRBTPLKJHTHTNJMActual

285495443413628,533Total

13228352923,51600DE

11,53,500,000,000,000,008,000,00QA

6812,0012,006,0012,0012,009,005,00LE

20,000,001,000,001,000,000,00TD

30,000,000,000,000,000,003,00RE

68,55,507,007,005,507,0011,5025,00PM

TotalRBTPLKJHTHTNJMPlanned

11

T-76.4115 Iteration demoT-76.4115 Iteration demo

Resource usage

Project is on its track but under its budget

Lower than expected resource usage in the S1 & S2 will give us more slack for the rest of the project

The challenge is to use this slack: => Holidays can be utilized.

Original plan (in the beginning of the iteration)

Realization and updated plan

(realized hours and updates)

631112106,581779885,571I2

21433473545,51516,521,5S2

1330190190190190190190190Total

202,5211634343436,527S1

3702420,539,533,54351,571PP

SUMRBTPLKJHTHTNJM

5609699,573,581,57773,559I2

285485443413629,533S2

1330190190190190190190190Total

202,5211634343436,527S1

3702420,539,533,54351,571PP

SUMRBTPLKJHTHTNJM

12

T-76.4115 Iteration demoT-76.4115 Iteration demo

Quality dashboard

Documentation extensively reviewed and updated Wiki: Use cases selected for implementation have been

tested, some minor defects open MUPE: Explorative testing performed, usability not yet

sufficient Code reviews behind schedule, customer comments

needed

Legend

Confidence:3 = tested well

2 = tested

1 = looked at, but uncertain

0 = not tested at all

Quality:3 = quality is good

2 = quality is mediocre

1 = quality is bad

Part of the system Quality Confidence CommentsProject documents 3 3 Project plan and SEPA diaries reviewed and updatedWiki: Workbook 3 3 Selected use cases tested and implemented, only minor bugs openMUPE: Generic reader 2 2 Usability issuesCode reusability 2 2 Code reviews behind schedule, but otherwise codebase healthy

13

T-76.4115 Iteration demoT-76.4115 Iteration demo

Quality Metrics 1/2

Defect status:

Total defect count:I1 Wiki I1 Mupe I2 Total

Reported 47 3- 50Closed 13 0- 13Open 34 3- 37

Defect classification:Critical High Medium Low Total

Open 0 1 19 17 37Closed 0 0 11 2 13Total 0 1 30 19 50

Most defects logged are minor cosmetic defects or usability notes No critical defects logged, testing during development sufficient High severity TR029_MUPE: Old MUPE login does not work after server

restart, almost showstopper, but has a workaround

14

T-76.4115 Iteration demoT-76.4115 Iteration demo

Quality Metrics 2/2

Codebase size in LOCC (revision 304):I1 I2

Wiki (php) 3788 -Mupe (Java) 1553 -Mupe (XML) 524 -Total 5865 -

Other metrics and practices: Statistical metrics for the Generic Wikireader for MUPE:

http://b123.myrootshell.com/~tinurmin/s2_complexity/ Heuristic evaluation of usability for Wiki and MUPE

brought many improvement suggestions Explorative testing and extensive testing during

development

15

T-76.4115 Iteration demoT-76.4115 Iteration demo

Realized Risks

RI003: A team member may lack the skills needed in the project. Effect: A developer had challenges in getting started with his work. (S1,

severity: High) Effect: A bottleneck task was almoust complete for several days during. (S2,

severity: High) RI004: Communication between group members might be insufficient.

Effect: PM was unaware of problems that one developer had. (S1, severity: Medium)

RI007: Project servers might be down for a while. Effect: Wiki was not in use for a while. (S1, severity: Low)

RI009: There might be problems with communication channels. Effect: See above.

RI013: Sprint time schedule might be unrealistic. Effect: Some tasks were clearly late and the development had to be continued

parallel during the testing. (S2, severity: High RI014: Bottlenect tasks might hinder the project progress.

Effect: See RI003 RI019: Making modifications to Wiki might be unexpectedly challenging

S1 & S2 came a bit short of what was planned.

Work results

17

T-76.4115 Iteration demoT-76.4115 Iteration demo

Wiki status

Implemented: Data structure has been designed The most technically challenging functionality has been implemented

Many kinds of special pages Commenting functionality Shot scheduler Drag-drop sorting Basic call-sheet functionality

To be implemented: Call sheet to be finalized Version history GUI and navigational structure to be finalized based on customer comments

Lots of work in here!

18

T-76.4115 Iteration demoT-76.4115 Iteration demo

MUPE status

Implemented: Transfer WikiText to MUPE Working links Dividing article to subpages Upload: Commenting functionality & photo sending

To be implemented: MUPE-parser: Usability & Heuristics Authentication?

Used work practices

20

T-76.4115 Iteration demoT-76.4115 Iteration demo

Most important work practices

Time reporting (Excel-sheets) Status reporting:

Backlog used as a part of status reporting => wasn’t of much use, since S1 there was no budget pressure

Communication Few face-to-face meetings used in S1, Many Skype meetings in S2 Challenges in communication during S1 => Regular Skype meetings solved

this problem in S2. Documenting

All the documents in team Wiki, has functioned well Document version control in Wiki Early victory

"Easy thing first, the most business critical second" turned more into "Easy thing first, the hardest second”, but was nevertheless a useful approach

Process improvement What did we learn?

Which methods were worth using and which were not? What problems did we have?

Whas the problem caused by us or some other stakeholder? What can we do better?

Which methods should be try using in the next sprint?

S3 Goals

22

T-76.4115 Iteration demoT-76.4115 Iteration demo

S3 Goals (to be discussed with the customer)

Finalizing the functionality currently under work in Wiki + new requirements received from the customer

Enhance the usability of both MUPE and Wiki GUI so that the first ”production” version of the software would be ready at the end on S3

Continue SEPA work

Thanks for your interest!

Questions?