T76.115 Project Review

1
T-76.115 Project Review

• RoadMappers
• PP Iteration29.10.2003

2
Agenda

• Project introduction (3 min)
• Project status (10 min)
• achieving the goals of the iteration
• project metrics
• risks
• Used work practices (10 min)
• Completed work (10 min)
• Plans for the next iteration (5 min)

3
Project introduction

• Background of the project
• Project is being done for the Sarcous research
  project in the SoberIT laboratory
• Purpose
• Create a graphical user interface for a modeling
  tool for configuration tasks
• Project organization
• Group Pohjola (PM), Enbuska, Karkkunen, Latto,
  Saastamoinen, Sarmanne, Siltanen
• Customer Tero Kojo
• Technical advisor Mikko Multimäki
• Mentor Joonas Iivonen
• Project goals
• Learn
• Deliver quality software

4
Status of planned goals of the iteration

• Goal 1 Specify the goals of the project
• OK
• Goal 2 Project Planning
• OK, excluding iterations I2, I3, DE, which have
  not been planned in detail
• Goal 3 Requirements specification including use
  cases
• OK, requirements specification is ready and
  accepted by the customer
• Goal 4 Select and adapt work practices to be
  used in the project
• Partially OK, some work practises cannot be
  started yet and some are improved in next
  iteration
• Goal 5 Make the contract with the customer
• Not yet signed by the group, but project plan
  accepted on both sides contains rights to project
  outcome

5
Status of planned deliverables of the iteration

• Project Plan
• OK, except planning of iterations I2, I3 and DE
• Requirements document
• OK
• Quality handbook
• OK, contains most important work practices
• Will most likely evolve during the project

6
Realization of the tasks

• Started tasks

• Reasons for major discrepancies
• estimation problems especially in requirements
  documentation
• lecture attendance was estimated 100 which is
  optimistic
• project review has not yet realised
• There is usually some space upwards in estimates

7
Working hours by person
Realized hours in this iteration
Plan in the beginning of PP iteration
Plan in the beginning of I1 iteration

• Bulk estimates at the beginning of iteration
• Lecture attendance lower than estimated
• Estimates have been updated due to more
  information available

8
Quality metrics

• Main quality metrics to be used in the project
• Code size
• Amount of bugs
• Amount of usability problems
• Work hours
• Project progress (burndown)
• Time spent on bug fixes

9
Risks

• Special risk management task force is attending
  the risk management course (Enbuska, Sarmanne,
  Siltanen)
• The responsible person for risk management in
  this project is Samuel Siltanen
• Whole group had a brainstorming session on risks
• Task force wrote risk management plan
• Assigned a responsible person for every risk
• The risks are reviewed once in an iteration
• No risks have yet been materialized

10
Work practices

• Used work practises presented in the quality
  handbook
• Communication
• Internal meetings
• Other communication
• Communications with the customer
• Communication with mentor
• Process improvement
• Requirements management
• Gathering requirements
• Change management
• Reporting
• Time
• Bugs
• Testing (planned in more detail in next
  iteration)
• Personal SE assignments
• Progress tracking and control (Pohjola)
• Configuration management (Latto)
• Refactoring (Siltanen)
• Heuristic evaluation of GUI (Karkkunen)

11
Experiences on started practises

• Communication
• As a whole has worked well, needs still some
  focusing to avoid excess amount of e-mails
  received by the group members
• Meeting minutes will be written starting from
  next iteration
• Process improvement
• Improvements will be discussed in first meeting
  of iteration I1
• Hour reporting
• Project progress control requires also the
  reporting of effort left in a task
• Some hours have been lost in the Trapoli system
• Version control (Configuration management)
• CVS has been set up and use guidelines written
• Assignment practises will mostly start at the
  beginning of next iteration

12
Gathering requirements

• 3 members of the group formed the requirements
  team Saastamoinen (responsible), Enbuska,
  Karkkunen
• The gathering of the requirements was done with
  an iterative process containing elicitation,
  analysis, documentation and validation phases
• First meeting and interviewing the customer
• The data collected is then analyzed and
  documented as requirements and use cases
• Document was represented to the customer and
  validated in the next meeting
• The interviewing and discussion continued
• final requirements document
• Overall
• the practice was found very useful and effective
• In the coming iterations we will concentrate on
  change management

13
Results of the iteration

• Status and contents of these documents has been
  discussed in more detail earlier in this
  presentation
• Project plan
• Quality handbook

14
Results of the iteration Requirements document

• Requirements document
• Purpose
• Tool for observing the project progress
• Agreement between group and customer
• Goals
• To create a graphical user interface
• System overview
• Background
• System
• User requirements
• Documented as Use cases
• Functional requirements
• Based on information from Use cases
• Properties
• quality requirements or non-functional
  requirements
• Constraints

15
Plan for the next iteration

• Goals
• design core architecture
• design userinterface on general level
• implement some basic use cases
• First UC-01, UC-05, UC-06, UC-07, UC-08, UC-09,
  UC-10, UC-11, UC-12, UC-25
• Optional use cases UC-02, UC-03, UC-04
• Deliverables
• updated project plan
• tech. specification (core architecture)
• test case specifications
• usability test plan
• test plan
• test report
• progress report (slideshow)
• Risk Interface to existing tool is not ready yet
  (delivered by customer)
• Schedule
• Requirements analysis 0,5 wk
• Design and test planning 1,5 wk (interface design
  continues)
• Implementation and testing 2 wk

16