T-76.115 Project Review Tetrastone Projext Planning Iteration 27.10.2003.

T-76.115 Project Review

TetrastoneProjext Planning Iteration

27.10.2003

2

T-76.115 Project ReviewT-76.115 Project Review

Agenda

Project status (5 min) achieving the goals of the iteration project metrics

Used work practices (5 min)

Completed work (5 min) The results of this iteration will be presented

Plans for the next iteration (5 min) Tasks Features that will be implemented

Discussion

3


Status of planned goals of the iteration

Goals of the project from all perspectives

Customer’s goals – The customer has identified their main goals for the project and the information has bee delivered to the group

Goals can be found from the project plan

Group’s goals – The project group has agreed an certain set of common goals for the project.

Can be found form the project plan too.

Select and adapt work practices to be used in the project

Work practices used during the project have been defined and some have already been used.

There has been no need to use all defined practices yet

Make the contract with the customer Ok

4


Status of planned deliverables of the iteration

Project Plan OK and Accepted, but... Detailled tasks for iterations 2, 3 and Delivery will be updated during the

project.

Requirements document OK and Accepted both by the customer and the project group

Risk management plan Delivered together with the project plan

Use cases So far Use cases 1-15 defined All cases accepted by the customer Documented in the Requirements Specification

5


Realization of the tasks

Summary:

Planned 200 hours – realized only 161.5 38.5 hours were realized less than was planned Of course that is better than vice versa! Few tasks were underestimated

Requirements documentation Project Plan writing

Problems:

Hard to estimate all the tasks needed A lot of general work Project was just starting

Solution:

Defining the task more accurately More detailled plans in the next iterations

name realized planned

GE: Meetings (customer) 28.50 100

GE: Meetings (internal) 3.50 100

GE: Server installation and setup

11.00 15

Realized hours (other/ALL iterations' tasks)

Realized hours (PP iteration tasks)

name hours_done planned diff hrs_left

DS: Req. documentation

14.00 10 4 0.00

DS: Req. elicitation and analysis

6.50 10 -3.5 0.00

DS: Study domain RosettaNet

3.00 10 -7 0.00

DS: Study technology XML/.NET

3.50 10 -6.5 0.00

GE: Lectures 40.00 50 -10 0.00

GE: Meetings (mentor) 12.00 20 -8 0.00

PM: Define project goals 2.00 2 0 0.00

PM: Other project management

5.00 5 0 0.00

PM: Plan work methods and tools

5.00 15 -10 0.00

PM: Start and organize project

5.00 10 -5 0.00

PM: Write progress report 2.00 3 -1 0.00

PM: Write the project plan

19.50 15 4.5 0.00

TOTAL HOURS PLANNED

Total 161.50 200

Total hours realized in the PP-iteration

6


Working hours by person

Kjell had some extra work with the Req. Spec. as well did Mikko with the Project Plan.

Usually only some part of the group was in the meetings and that’s why not all the planned hours realized.

Plan in the beginning of this iteration Hours realized per member

MEMBER HOURS

Mikko 49.00

Kjell 39.50

Anssi 15.50

Kimmo 15.00

Henry 11.00

Mikael 24.50

Hanna 9.00

Less studying than was planned :(

Hours were a little bit over estimated

7


Changes to the project

So far no changes to the project has been made

So far no changes can be seen in the horizon

8


Risks

Risk management of this project is made by a separate risk management group

This group attendeeds course:T-76.633 Special Course in Software Engineering: Risk management

Risk have been identified and documented in the Risk Management Plan

What is the current situation regarding the risks?

Materialized risks - None New risks identified - Basically all, since they have only now been identified

9


Work practices

So far the following practices have been used: Time reporting Documentation and document delivery Meetings Communications Risk management Etc.

The practices have been found good, since: They provide methods to easier control the project Bring consistency into the documentation, meetings, communications etc. They somewhat tell everybody what to do and what are the responsibilities

The practices used will be updated during the project if: Some practive does not suite to the group or the customer Someone comes with an idea of a new practice Some practice could be better

10


Example: Communications

The rules for communications was first published: E-mail conversations is done via [email protected] address Documents will be published in the group’s homepage

www.hut.fi/~mpsavola/Tetrastone Project manager / Account manger hadles the communications between the

group and the customer Document templates were published

The rules have been used so far quite succesfully Everybody knows the rules Document outlook is consistent Information is delivered to all stakeholders

Negative experiences Communications within the group could be done more efficiently The e-mail based communications delay is sometimes quite high Every body should have access to the WWW-pages

Summary The documentation practice is very usefull The practice will not be modified

11


Results of the iteration

The project group was succesfully formed

The group managed to get an agreement of the subject

And the group got the subject they wanted.

A first contact and a communications chain between the customer and the group was established

The domain and case were presented by the customer and understood by the project group

’Physical’ results: Project Plan Requirements Specification Risk Management Plan

12


Example: Project plan

Introduction Tells the background of the project and introduces the case

Stakeholders and Staffing Tells who are participating in the project

Goals and Criterion What is the wanted outcome End and about criteria

Resources and Budget How much resources can be used? And what resources are available

Work practices and tools How will different tasks be done during the project

Phasing How is the project divided in the timeline

Risk management plan Risks, propabilities and countermeasures

13


Example: Architecture overview

14


Plan for the next iteration Goals

Map almost all of the requirements To get better understanding of the

system Some code written Detailed design of support

functions and PIP document processor

Detailed design of data base and file system

Deliverables Updated Project Plan Updated Requirements

Specification Technical specification Test cases Test report and test log Progress report

Customer deliverables Initial version of the GUI Use cases 01-06 (UC-06 initially) Database and file systems

name effort responsible

DO: Updating requirement specification 5 kpholmbe

DS: GUI design 10 hniveri

DS: Technical specification 30 ALL

DS: Technical specification writing 10 ALL

GE: Meetings (customer) 20 ALL

GE: Meetings (internal) 20 ALL

GE: Meetings (mentor) 10 ALL

IM: Database and file system 20 ALL

IM: GUI implementation 20 hniveri

IM: Use Case 1 5 ALL






PM: Other Project planning 10 mpsavola

PM: Personal SE practice 20 ALL

PM: Progress report 5 mpsavola

PM: Project review and preparation 10 mpsavola

PM: Updating project plan 5 mpsavola

PM:Plan the next iteration 5 mpsavola

TE: Designing test cases 5 ALL

TE: Testing 20 ALL

TE: Writing test cases and log 5 ALL

15


Thank you

Any questions?

T-76.115 Project Review Tetrastone Projext Planning Iteration 27.10.2003.

Documents

Transcript of T-76.115 Project Review Tetrastone Projext Planning Iteration 27.10.2003.