Download presentation
Presentation is loading. Please wait.
Published byPeregrine Osborne Modified over 8 years ago
1
T-76.115 Project Review MTS [PP] Iteration 1.11.2004
2
T-76.115 Project Review 2 Agenda Project status Introduction to the project The goals of the phase Deliverables Relization of the tasks Quality assurance Risks Work results Project plan Draft user requirements Risk documents Used work practices
3
T-76.115 Project Review 3 Introduction to the project The purpose of this project is to develop and produce software to a new mobile terminal demonstrator. The main target will be to implement new input methods in mobile devices. Parties involved: Nokia R&D HUT machine design team for the HW SW team Software development will most probably include the design and implementation of a mobile user interface The final product of the whole project will be a functional mobile terminal demonstrator The software will be developed in C language
4
T-76.115 Project Review 4 Status of the Planing’s goals Goal 1: Specify the goals of the project from all perspectives OK The group’s and customer’s objectives have been identified Goal 2: Select and adapt work practices to be used in the project Ok, the practices have been chosen Iteration planning, time reporting, documenting, risk management have been practiced Goal 3: Make the NDA with the customer Moved to later, because the version need to be confirmed
5
T-76.115 Project Review 5 Status of the deliverables Project Plan OK, except chapter 6.1 because the requirements are still in the negotiation stage, so the implemention schedule can not be planned sufficiently at the moment. 5.2 The quality assurance plan in the iteration level is also not very clear due to the pending functionality specifications Requirements document Some basic functionalities are identified after meeting the HW team The most important ones have yet to be decided The final decision from the customers is necessary The non functionalities requirements have been identified The further features could be agreed later
6
T-76.115 Project Review 6 Realization of the tasks Explain the reasons for major discrepancies The estimation is not very accurate The lecture time is reserved too much for the English speaking students The the technology requires more learning time than expected Deferred definition to the requirements requires more meetings Unclear definition to the meeting types Unplanned work: risk management and requirement documents allocated to some members
7
T-76.115 Project Review 7 Working hours by person The work is deferred by the requirements More time spent on finding the answers than solving the problems Technical things like the architecture is not realized in the phase, so some people work less than planned Realized hours in this iteration Planed hours in this iteration
8
T-76.115 Project Review 8 Quality metrics Bug metrics Bugs of different testing techniques
9
T-76.115 Project Review 9 Quality assessment Other approaches in Quality Assurance: Clear and uniform coding standard collecting continuous feedback from the customer
10
T-76.115 Project Review 10 Risks The current situation regarding the risks: Identify and review risks at each milestone Assign the risks to the owners Prioritize risks based on seriousness and probability 3 risk categories: management, technology, product management
11
T-76.115 Project Review 11 Results of the Project Planning The major deliverables of the iteration, e.g., the following Project plan User requirements QA approach at the general level Risk management documents
12
T-76.115 Project Review 12 Project plan Present the following Stakeholders and staffing
13
T-76.115 Project Review 13 Project Plan Project goals: Resources: Each member have 190 hours for the project Linux operating system and C programming language will be used Renesas simulators as the developing environment and hardware emulator as the testing environment (Renesas) GCC C compiler, CVS and CUT, an open source software, will also be involved
14
T-76.115 Project Review 14 Used work practices The use of the planned work practices: Iteration planning Time reporting Version control Documenting Risk management Project review SEPAs Jiang Yihua – Meeting practics Chen Jie & Chen Ying – test-driven development Henri & Janne – Pair programming Guo Bofei & Zhou Hu – static methods The other practices considered: Defect tracking Peer testing The other practices will be used and reconsidered when the project progresses
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.