1 / 17

T-76.115 Project Review

T-76.115 Project Review. RoadMappers I3 Iteration 17.3.2004. Project status (10 min) achieving the goals of the iteration project metrics Used work practices (5 min) Completed work (20 min) presenting the iteration’s results demo Plans for the next iteration (5 min). Agenda.

micheal
Télécharger la présentation

T-76.115 Project Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.115 Project Review RoadMappers I3 Iteration17.3.2004

  2. Project status (10 min) achieving the goals of the iteration project metrics Used work practices (5 min) Completed work (20 min) presenting the iteration’s results demo Plans for the next iteration (5 min) Agenda

  3. Status of planned goals of the iteration • Goal: Finalize user interface design • OK • Goal: Finalize user interface • Implementation OK, needs debugging • Goal: Test system • OK • Goal: Peer group tests our system • OK • Goal: Test peer groups system • OK

  4. Status of planned deliverables of the iteration • Implemented use cases and core parts • Finalize modules and interface • OK, still some debugging needed • Documents: • Test report and test log - OK • Peer test plans (plans prepared for the peer testing group and plans prepared by the peer testing group) - OK • Peer test reports (report made by the peer testing group and report made for the peer testing group) - OK • Updated user's manual – OK, some updates in DE phase • Progress report - OK • Updated documents - OK

  5. Realization of the tasks • Very little time to do refactoring and unit tests • Hours were instead used in defect fixing • Defect reporting took more time than estimated because several persons participated and reporting is time consuming • Only infra-task was not started • Some tasks were overestimated on purpose to avoid surprises

  6. Working hours by person 1/2 Realized hours in this iteration • Debugging was major task in this iteration (Enbuska, Latto, Siltanen) • Effort divided unevenly • Chance to correct this in delivery phase

  7. Working hours by person 2/2 Plan in the beginning of this iteration Latest plan

  8. Quality metrics 1/2 Usability problems • Usability testing • In the middle of iteration • With 4 users • Heuristic evaluation • Done towards the end of iteration • Two evaluators

  9. Quality metrics 2/2 Bug metrics • System test cases: • Total cases 81 • Executed 71 • Pass/Fail 36/35 • Unit tests: • No new tests made • Old ones slightly updated • Tests/fail - 55/1 • 1 critical • Null pointer exception from 8 tests

  10. Quality assessment • The item pass/fail criteria for unit level had to be ignored to be able to start system level testing. • The following test cases could not be executed for different reasons: TC-1-04, TC-1-05, TC-1-12, TC-1-14, TC-3-13, TC-4-06, TC-4-12, TC-4-13, TC-5-04, TC-5-05. Legend Coverage: 0 = zero coverage 1 = poor coverage 2 = adequate coverage 3 = good coverage 4 = excellent coverage 5 = full coverage Quality: J = quality is good K = not sure L = quality is bad

  11. Software size in Lines of Code (LOC)

  12. Risks • No new risks were identified during this iteration • 2 risks have materialized (ID, weight 1-100, rank) • The product quality (R15, weight 18, #8) => More effort to bug fixing • A group member absent (R2, weight 15, #12) => Tasks shared with other group members • All of these have been reacted or the risks effects are minimized • Low amount of materialized risks? • Learned to control them • Some risks are more significant than others

  13. Work practices • Used practices were reported in I3 mentor meeting • Planned practices were • Project progress tracking and control • Hour reporting • Communication practices • E-mail • Internal meetings • Talk • Wiki • Requirements management • Design patterns • Configuration management • Coding conventions • Refactoring • Quality assurance • Document reviews • Automated unit testing • Bug reporting • Usability testing • Heuristic evaluation • No major changes to practices were made

  14. Results of the iteration • Deliverables were discussed in the beginning • No new results • Old documents updated • Next - demo

  15. Demo • “No to something completely different…”

  16. Plan for the next iteration • Goals • Fix remaining defects and finalize system • Finalize project documentation • Delivery of system • Evaluate own work • Hold final meeting • Deliverables • Fix known bugs • Bugs are prioritized • Final report • Test report and log • Final versions of alldocuments produced during the project

  17. Timeline • Week 12 • Debugging – Tuomo&Samuel&Jan • Testing - Mikko • Update User Manual – Sanna&Marko • Week 13 • Debugging - Tuomo&Samuel&Jan • Update User Manual - Sanna&Marko • Delivery of the system to the customer • Write final report - Eila • Week 14 • Acceptance testing - Customer • Write final report - Eila • Finalize documents - All • Week 15 • Final demo and preparation

More Related