T-76.4115 Iteration Demo Tikkaajat [PP] Iteration 18.10.2007.
-
Upload
coral-mcbride -
Category
Documents
-
view
228 -
download
0
description
Transcript of T-76.4115 Iteration Demo Tikkaajat [PP] Iteration 18.10.2007.
T-76.4115 Iteration Demo
Tikkaajat[PP] Iteration
18.10.2007
2
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda Project status (10-15 min)
achieving the goals of the iteration project metrics
Work results (20-25 min) presenting the iteration’s results
Used work practices (5 min)
3
T-76.4115 T-76.4115 IterationIteration demo demo
Introduction to the project jEhIntranet System
Informational logistic solution for Eduhouse Oy
coordinating system for customers, employees, and operations
4
T-76.4115 T-76.4115 IterationIteration demo demo
Introduction to the project jEhIntranet System
Current system allready exist
Extended over time Overlapping Cluttered code Low speed functionality
Lack of documentation
The basic idea is to re-develop the current system as ready as possible
Using Java language and different techniques Hibernate, Velocity, Ajax
Documentation for furher development
5
T-76.4115 T-76.4115 IterationIteration demo demo
Status of the iteration’s goals Goal 1:Project planning
OK
Goal 2: Understanding the domain OK
Goal 3: Requirements specification on general level including most important functional requirements and use cases
OK
Goal 4: Selecting appropriate tools OK
Goal 5: Setting up the development environment OK
Goal 6: Defining working practices OK
Goal 7: Training in the development environment OK
Goal 8: Preliminary database description OK
Goal 9: Preliminary architecture OK
6
T-76.4115 T-76.4115 IterationIteration demo demo
Status of the iteration’s deliverables Project plan
OK, except chapter 5.2, because quality assurance plan will be separated document delivered 2.11
Requirements document OK, all important requirements documented in general level
SEPA diaries (at least ch. 1) OK
Instructions and guidelines for development (communication, coding, reporting)
OK
Preliminary database description document OK
Preliminary architecture document OK
7
T-76.4115 T-76.4115 IterationIteration demo demo
Realization of the tasksStatus Realized Planned Diff (Left)
Project Planning Ok
Task 1. Planning and decision making Ok 24,5 51 - 26,5 26,5
Task 2. Documentation Ok 25,5 22 +3,5Requirements Engineering OkTask 3. Elicitation, analysis, priorization, validation
Ok 18,5 28 -9,5 9,5
Task 4. Documentation Ok 18 12 +6Training Ok 159 149 +10
Preliminary database description Ok 17,5 21 -3,5 3,5
Preliminary Architecture description 14 16 -2 2
Meetings Ok 95 90 +5
Management Ok
Task 5. Project tracking Ok 6 3 +3
Task 6. Arrangements Ok 19,5 8 +11,5
Unclassified tasks Ok 42,5 75 -32,5 32,5
SEPA
Task 1 Pair Programming (ch 1) 4 20 -16 16
Task 2. Automated Unit Testing (ch 1) 3 30 -27 27
Total 447 525 -78 78
8
T-76.4115 T-76.4115 IterationIteration demo demo
Resource usage
TL TH SM VS ST VH TM TI YZ SUMPP 82 89 72 57 42 60 46 41 36 525I1 65 60 32 67 38 82 72 65 44 525I2 43 41 46 66 70 48 72 44 70 500Total
190 190 150 190 150 190 190 150 150 1550
Original plan (in the beginning of the iteration)
Realization and updated plan
(realized hours and updates)
TL TH SM VS ST VH TM TI YZ SUMPP 71 73,5 56,5 49 19 67 36 42 33 447I1 76 75,5 47,5 75 61 75 82 64 47 603I2 43 41 46 66 70 48 72 44 70 500Total
190 190 150 190 150 190 190 150 150 1550
9
T-76.4115 T-76.4115 IterationIteration demo demo
Risks Top-level risks
(of total 16)
10
T-76.4115 T-76.4115 IterationIteration demo demo
Results of the iteration Project plan
Project plan document
Requirements User requirements document
Preliminary system architecture Preliminary architecture Preliminary database description
11
T-76.4115 T-76.4115 IterationIteration demo demo
Project plan Stakeholders and staffing Project goals Project resources (hardware and budget) Project practices and tools Phasing
12
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan Stakeholders
13
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan Project goals
Database of the current system needs to be improved and implemented entirely (Prior 1)
Improved means that the DB is more uniform Implemented means that the DB is designed, implemented and tested
All needed data is in the implemented DB Queries has to be at least as fast as current DB is
Software engine has to be maintainable and expandable and some functionality from the current system has to be implemented (Prior 2)
Core functionality for the personnel and trainers Verification against test cases and guidelines
Improved graphical user interface has to be implemented for the implemented engine parts (Prior 3)
Verification against test cases
14
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan Project resources
Hardware One server from the customer Personal Computers used in the development
Budget Salary for team members 20€/h, for mentor and technical expert 30€/h
15
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan – practices and tools Practices
1) Iterative development and planning Iteration planning in the end of last iteration
Goals, deliverables – customer validation Sprint planning in the end of last sprint
Tasks are frozen during sprints
16
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan – practices and tools Practices
2) Risk management
Identify Stakeholders involved Brainstorming
Analyzing Probability Impact
Controlling actions Avoid or reduce the effect of risk
Monitoring Risk situation Status of controlling actions Constantly monitored Documentation updated when needed
17
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan – practices and tools Practices
3) Communication Cell phone - critical information Email - important information IRC - realtime communication Weekly meetings – ensures that relevant information reaches all
partisipants MediaWiki - all public documentation (guidelines, minutes, etc.) reachable
18
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan – practices and tools Practices
4) Defect tracking Found defects are reported, unless they are immediately repairable Defects are prioritized and they are ranked by impact value Defects are given for fixing to developers according to impact value Fixed defect is reported
5) Time tracking Weekly reporting and tracking Software tool used for reporting
6) Documentation Against templates Same format (deliverables in PDF, others in DOC)
7) Coding conventions Specific guidelines published in MediaWiki
19
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan – practices and tools Tools
1) Management MediaWiki, used for group presentation, communication and some
document preparation Bugzilla, maybe used for issue tracking Weekly reporting tool, used for reporting working hours for status tracking
and other project management tasks. Implemented by project manager and running on his server.
MS Office programs (Excell, Word, PowerPoint)
2) Development Eclipse, used as integrated development environment Ant, used as build tool for the project Subversion, used as version controlling tool
20
T-76.4115 T-76.4115 IterationIteration demo demo
Project Plan - PhasingjEhIntranet
1550 h
1. Iteration (3 weeks)
447 h (realized)
2. Iteration (7 weeks)
603 h (planned)
3. Iteration (7 weeks)
500 h (planned)
Iteration plan Iteration plan
Implementation
Project plan
Requirements engineering
Quality assurance
Documentation
Iteration plan
Implementation
Quality assurance
FinalizationTraining
Documentation
Architecture
Documentation
Test reports
Peer testing
Architecture
Management
Management
Management
Requirements engineering
21
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements Business goals Main domain concepts User groups Functional and non-functional requirements
22
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements – business goals Current system is very complex
Further development almost impossible Very risky to add new features
Solution
Reconstruct the whole system Expandable More easier to modify More uniform
23
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements – main domain concepts
24
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements – user groups
25
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements
functional and non-functional requirements
Most important functional1. User can login to system2. User can logout from system3. Personnel can add courses4. Personnel can add customers5. Persinnel can see upcoming courses using the calendar
Most important non-functional requirements1. Database is uniform2. System is modifiable3. System is extendable4. Only registered users are allowed to use the system5. Personnel may have different priviledges
26
T-76.4115 T-76.4115 IterationIteration demo demo
Used work practices How have you been using the planned work practices, what are the experiences of
Project tracking is more time consuming than predicted
More resources to the development in the viewpoint of quality. Prototyping teached us
Coding conventions Testing Pair-programming is effective way to implement modules and to share
experiences
Schedule is hard to fit to serve all participants
Weekly meetings are a good way to share information
Weekly reporting Reporting needs to be focused to planned tasks
Too detailed tasks? Frustrating if slacks in reporting tracking needs to be done multiple times
Version control Guidelines needs to be defined
Data-losses new risk identified
Process improvements Adopting Skype in the upcoming iteration?