T-76.115 Project Review

T-76.115 Project Review

BigBrotherPP Iteration

3.11.2004

2

T-76.115 Project ReviewT-76.115 Project Review

Agenda

Project introduction (5 min) Project team Project customer Project goals

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

Work results (10 min) presenting the iteration’s results

Used work practices (5 min) Next iteration planning (5 min) Discussion

5 min 10min 10min 5min 5min

1

3


Introduction to the project

Customer: Beconnected Finland Ltd. Produces IP-based video surveillance systems for international market Main product: ASAN = Automatic Surveillance and Alarming Network Customer representative: PhD Michael Samarin

Project team: Aino Lahdenperä, Maija Kangas, Outi Syysjoki, Janne Ojala, Antti Alestalo,

Juhani Nokela, Ville Vatén GOAL: Produce tools, which help Beconnected in their customer support

work and reduce costs through increased productivity Three tools will be created:

Watchdog – Automatic monitoring of network cameras HourLogger – Log support person’s work hours per customer/target LogAnalyzer – Search for error patterns from ASAN logs

Beconnected’s goals: Working software is the only thing that matters KISS – Concentrate on simplicity, maintainability, quality. No fancy features Very busy making business – we should bother them as little as possible Minimize costs – all costs should be covered by the attendance fee to SoberIT


4

4


Overview of the problem domain


5

5


Status of the iteration’s goals

Goal 1: Get to know the customer and their goals for the project. OK

Goal 2: Learn their working methods and tools. Not as important as assumed

Goal 3: Synchronize mutual project goals, methods and schedule between the customer, project team and course staff.

OK. Goal 4: Plan the project and write the project plan

Not 100%, but close enough for this phase Goal 5: Gather customers requirements from customer and write initial

requirements specification document OK

Goal 6: Study the application domain and familiarize the project team with the concepts and challenges in it.

OK for those who have been able to attend all customer meetings Goal 7: Set up all the needed tools and environments for communication,

documentation and programming. OK, except development server from students’ own resources not available


7

6


Status of the iteration’s deliverables

Project Plan OK, except some minor tuning needed QA plan will be delivered 9.11.

Requirements document Only a few most important use cases written in detail

More use cases will be added in the next iteration Watchdog

OK, enough to start design and implementation HourLogger

OK, enough to start design and implementation LogAnalyzer

OK, enough to start design and implementation Non-functional requirements

OK, but might still need some work with the customer.


8

7


Realization of the tasks


10

Major discrepancies Lectures: people didn’t attend as much

as expected (Tools: PM was alone!) RE: much of the elicitation was done in

project kick-off meeting and review was performed by email.

Internal status & planning meetings very efficient, some planning work moved to project plan writing sessions

Customer preferred emails and we try to avoid meetings

Write project plan Includes a lot of other planning

work too Writing in English is slower than

expected HW/SW problems…

Not started: SEPA practices not started yet Much of the work was included in

the project plan writing Extranet not as complicated as

expected

8


Realization of budget

Monthly allowance of € 100 for miscellaneous well justified project costs

October costs: € 1 for mailing the NDAs $ 43 for buying Core Servlets and JavaServer Pages, Vol. 1 from Amazon


11

9


Working hours by person

The personal work distribution was NOT planned in the PP-iteration plan. This reflects the situation of the plan a week ago.

Ville put more work in RE than originally estimated. Work distribution among members not satisfactory

More equal task delegation will be performed in future

Realized hours in this iteration


12

10


Working hours by person

No other problems than Ville’s extra work. No implementation tasks assigned to Ville

Moved 5 Aino’s hours from FD to I1.

Other updates are minor

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

Latest plan (inc. realized hours and other updates)


13

11


Quality assessment

Functional area Coverage Quality Comments

Requirements Document

2 Has been reviewed

Project Plan 1 Has not been thoroughly reviewed

Development Environment

2 No development server available yet

Legend

Coverage:

0 = nothing

1 = we looked at it

2 = we checked all functions

3 = it’s tested

Quality:

= quality is good

= not sure

= quality is bad


14

12


Risks

Risks Development environment

No server computer currently available! English is used as the primary project language More work used than planned, especially Ville NDA is very strict

We can not publish something critical to the course We publish something that breaches the NDA

Busy schedules among group members Potential communication problems Quality problems among team member deliverables


15

13


Results of the iteration

Project Plan

Requirements Document

Demonstration


16

14


Project plan

Stakeholders and staffing (next slide) Project goals (discussed before)

Special attention to the verification criterias has been given Project resources (discussed before) Project practices and tools

Iterative and incremental development Use-case driven development Chief engineer centered development and group sessions Communication through mails and Wiki Meetings: efficient, good meeting minutes, avoid meetings Work hour logging: strict, needed for the course SEPA: Pair programming, Usability tests, Design patterns, Meeting practices Development server will be set up completely by project team

Only the network cameras required from Beconnected No other hardware, software, libraries, tools etc. provided by Beconnected.

Phasing overview Watchdog and HourLogger core functionality in I1 LogAnalyzer in I2 Minimum requirements ready at the end of I2


18

15


Project Plan (continued)

Stakeholders and their relations


20

16


Requirements document

Watchdog Monitors status of network camera on predefined intervals Alarms when malfunction occurs Allows user to configure the monitoring parameters, including ASAN server

database authentication data Records historical data of network camera statuses and erases old data Presents data in illustrative form

HourLogger Logs technician's work hours per customer, per target and per work type Provides statistical analysis of the recorder work hours Provides output filter for comma-separated list for the recorded work hours

Log Analyzer Parses ASAN Server logs for error patterns Provides overview and browsing of log events Allows user to configure log analyzer parameters

Non-functional requirements Clear, measurable Check with customer about the levels of the qualities is needed.


23

17


Demonstration

Demo of network cameras for the development purpose of this project Originally, this demo was planned to be performed through our

development server to demonstrate the availability of all development tools.


25

18


Used work practices

Time reporting in Trapoli Difficulties in dividing working hours into concrete tasks and work types

Version control with CVS Now in CC-work, before some quota problems

All documentation in HTML Problems with Word HTML, Trellian…

Meetings Laptop is pop => good meeting minutes

Risk management Has started

Requirements elicitation and analysis Informal, unstructured interviews with the customer Brainstorming

Group working sessions Project plan writing Requirements analysis & representation & validation sessions

Publishing policy NDA causes extra overhead


30

19


Iteration I1 Goals

Generic goals: Development environment fully up and running Requirements document actively maintained and requirements detail level is

raised Watchdog goals

Architectural & UI & detailed design Background process implemented and tested Main view implemented and tested Background process configuration implemented and tested

HourLogger goals: Architectural & UI & detailed design Input view implemented and tested Overview view implemented and tested Configuration view implemented and tested

LogAnalyzer goals Architectural & UI design

SEPA goals: Pair programming sessions on most critical use cases Usability tests performed for the prototypes Design patterns used in the architectural and detailed design Meeting practices are reviewed and improved


34

20


Questions?


35

Date post:	21-Jan-2016
Category:	Documents
Upload:	aricin
View:	35 times
Download:	0 times

T-76.115 Project Review

Documents