T-76.4115 Iteration Demo

Team DTTProject planning (PP) Iteration

19.10.2005

2

T-76.4115 T-76.4115 IterationIteration demo demo

Agenda Project status (10 min)

achieving the goals of the iteration project metrics

Work results (20 min) Project plan Requirements document

Used work practices (5 min)

3

T-76.4115 T-76.4115 IterationIteration demo demo

Introduction to the X-Connector project (1/2) Domain: process simulation, simulation model with several simulation

engines (cluster)

Deliverables: a user interface for defining data exchange between the cluster members a test server environment for prototyping the data exchange accelerated data access (Fast data access) data synchronization scheme

Technology: web service technology based on OPC specifications user interface as an Eclipse plug-in

4

T-76.4115 T-76.4115 IterationIteration demo demo

Introduction to the X-Connector project (2/2) The customer of the project is VTT Industrial Systems

Prioritized objectives:1. User interface implementation and test server to store data exchange

connection information 2. Fast data access implementation for the test server cluster 3. Synchronisation implementation for the test server cluster

Team DTT’s initial objective is to succeed in accomplishing levels 1 and 2 However, with fixed schedule and available effort, the scope of the project may

be redefined during the project.

5

T-76.4115 T-76.4115 IterationIteration demo demo

Status of the iteration’s goals Goal 1: Project planning

OK: Documented in the project plan, reviewed by the customer Goal 2: Understanding the domain

OK: 2 meetings with the customer, requirements specification done Domain turned out to be quite complex and unfamiliar to all the group

members Still some clarification needed

Goal 3: Familiarize the team with required techniques OK: Tools are selected, aquired and communicated to the team; needed

specifications have been delivered to the developers Goal 4: Requirements specification on general level

OK: Requirements specification meeting with the customer, requirements document created

Feedback from the customer needed Goal 5: Assessment of the skills and special knowledge of the team

members OK: Internal kick-off meeting arranged, skills of the developers identified

6

T-76.4115 T-76.4115 IterationIteration demo demo

Status of the iteration’s deliverables Project plan

OK, except chapter 5.2 Quality assurance which will be delivered later Reviewed by the customer: feedback received, minor corrections made

Requirements document OK (possibly some corrections after feedback) All important functional (F1-F8) and non-functional (NF1-NF5) requirements

documented Sent to the customer for feedback 13 use cases specified on general level

Progress report: OK

Tool for effort management OK, Excel-based solution: easy to maintain, provides reports of the projects

status

SEPA diaries Topics: Meeting practices (introduction), Heuristic evaluation (introduction),

Refactoring (not started yet)

7

T-76.4115 T-76.4115 IterationIteration demo demo

Realization of the tasks (1/2) Status and effort distribution per task (17.10.2005)

Work types: PM (project management), DO (documenting), DE (design), IN (infrastructure), ST (studying)

ID Task Status Type Est. Real. Diff. Left1 Iteration planning ok PM 9 9 02 Iteration planning ok DO 3 3 03 Internal kick-off meeting ok PM 12 6 -64 Kick-off meeting with the customer ok PM 6 4 -25 Requirements specification meeting ok DE 12 8 -46 Establish project management practices ok PM 30 29 -17 Create project web site ok IN 5 3 -28 Creating the project plan ok DO 25 30 59 Creating the requirements document ok DO 30 23 -710 Kick-off meeting with the mentor ok PM 3 3 011 Read protocol specifications ok ST 5 4 -112 Acquire needed tools ok IN 5 2 -313 SEPA diaries ok SEPA 36 6 -3014 Progress report -presentation ok PM 5 5 015 Iteration demo unfinished PM 6 0 -6 616 Attending to the lectures unfinished ST 18 12 -6 617 Preliminary architecture plan unfinished DE 10 0 -10 10TOTAL 220 147 -73 22

8

T-76.4115 T-76.4115 IterationIteration demo demo

Realization of the tasks (2/2) Realized effort smaller than estimated (~170h vs. 220h)

Over-estimated: SEPA (-30h): Estimated 3 diaries, 12 hours each; realized 2 diaries 3 hours each

(only introductional parts) Requirements document (-7h) Internal kick-off meeting (-6h): Estimated 2 hours/person; realized 1

hour/person

Under-estimated: Creating the project plan (+5h): 3 authors, lots of work

9

T-76.4115 T-76.4115 IterationIteration demo demo

Working hours by person

Timo and Mikko didn’t start their SEPA, others used 1-3 hours to their diaries (6 hours budgeted)

Meetings were shorter than expected

Realized hours in this iteration

Member Estimated Realized Left DifferenceTeemu 70 57 4 -9Tomi 60 40 9 -11Dennis 60 40 9 -11Timo 10 3 0 -7Mikko 10 3 0 -7Ville 10 4 0 -6TOTAL 220 147 22 -51

10

T-76.4115 T-76.4115 IterationIteration demo demo

Working hours by person

Member PP SUM I1 I2 TOTALTeemu 70 70 50 50 170Tomi 60 60 50 60 170Dennis 60 60 50 60 170Timo 10 10 70 90 170Mikko 10 10 90 70 170Ville 10 10 80 80 170TOTAL 220 220 390 410 1020

Member Estimated Realized DifferenceTeemu 70 61 -9Tomi 60 49 -11Dennis 60 49 -11Timo 10 3 -7Mikko 10 3 -7Ville 10 4 -6TOTAL 220 169 -51

Realized hours in I1 iteration Plan in the beginning of this iteration

Latest plan

Member PP SUM I1 I2 TOTALTeemu 61 61 50 59 170Tomi 49 49 60 61 170Dennis 49 49 60 61 170Timo 3 3 75 92 170Mikko 3 3 92 75 170Ville 4 4 83 83 170TOTAL 169 169 420 431 1020

17 % 17 % 41 % 42 % 100 %

Plan in the beginning of the iteration was inaccurate

Plan was updated in the first week of the project planning

In I1, Mikko has more responsibilities than Timo (UI development); in I2, Timo has more responsibilities

17% of the effort used at the moment

11

T-76.4115 T-76.4115 IterationIteration demo demo

Quality assessment

Project plan was reviewed by the customer before the delivery

Requirements document has been reviewed only by the management team so far

Document has been sent also to the customer

Document Coverage Quality Comments

Project plan 2 Reviewed by the management team and by the customer. Minor corrections made based on the feedback.

Requirements document 1 Reviewed by the management team.

Legend

Coverage: 0 = nothing1 = we looked at it2 = we checked all functions3 = it’s tested

Quality:= quality is good= not sure= quality is bad

12

T-76.4115 T-76.4115 IterationIteration demo demo

Changes to the project Any other major changes to the project, not yet discussed

No major changes in sight at the moment

13

T-76.4115 T-76.4115 IterationIteration demo demo

Risks What is the current situation regarding the risks?

Risk log in the project plan: 9 risks with their effects, estimated impacts and probabilities, persons responsible

None of them realized so far

Identified risks A team member quits in the middle of the project or something happens

(accident, sickness etc.) New technologies cause problems The customer is developing some software components that will be used in the

project but fails to deliver them in time Project group doesn’t have the needed tools for the development Requirements change in the middle of the project Workload of the whole project is underestimated Workload of iteration I1 is underestimated and (software) deliverables won’t

finish on time Developed software components are incompatible One of the group members has difficulties to stay on schedule

14

T-76.4115 T-76.4115 IterationIteration demo demo

Results of the iteration Project plan

Requirements document

15

T-76.4115 T-76.4115 IterationIteration demo demo

Project plan Stakeholders and staffing

Project resources 6 persons x 170 hours = 1020 hours

Project practices and tools Eclipse, CVS clients, Borland Together 2006

and C++ compilers (gcc, .MS NET c++ compiler)

Phasing I1: User interface + test server, OPC DX I2: OPC DA, Fast Data Access, Syncronization

scheme

16

T-76.4115 T-76.4115 IterationIteration demo demo

Project plan Project goals

Customer:1. Functional and usable run-time view on the connections2. Functional and usable configuration view on the connections3. High quality user interface component that can be integrated easily to

other systems4. Well-implemented DXConfiguration interface and OPC XML DX Kit

(descriptions in technical specification document) 5. Technology to accelerate data exchange between the simulation cluster

members6. Test synchronization in the cluster7. Support for further development: clear and readable code and

documentation All the code follow coding conventions. Project group:

1. Pass the course2. Fulfill customer’s expectations3. Gain experience in software projects

17

T-76.4115 T-76.4115 IterationIteration demo demo

Requirements document Functional requirements (in priority order)

1. Create connections2. Browse connections3. Monitor cluster4. Group connections5. Configure cluster members6. Ability to automatically create two way connections7. Ability to remove connections8. Add/remove server

Non-functional reqirements1. Commit to OPC DA and DX standards2. UI must run as an Eclipse plug-in3. Provide Fast Data Access4. Ability for servers to auto select connection protocol5. Synchronization of data exchange in a cluster

18

T-76.4115 T-76.4115 IterationIteration demo demo

Used work practices Practices used in PP iteration

Iterative development: Ok Iteration planning: Ok, task list had to be updated after planning, effort needed

was overestimated Documenting: Ok, lots of work Risk management: Ok, risk log created Time reporting: Ok, effort management tool created Version control: Ok, all versions of the documents was published in project’s

web site Communication:

Serious problems with e-mail in internal communication: too many messages sent by the PM, slow/no response from others

Meeting practices: informal meetings, will be improved later (SEPA)

Practices going to be implemented in I1 Improved meeting practices (SEPA) New communication practices (TWiki, instructions for e-mail use, messenger)

detailed information in the project plan Heuristic evaluation (SEPA) Coding convention Defect tracking

19

T-76.4115 T-76.4115 IterationIteration demo demo

Thank you!Any questions?