1. T-76.115 Project Review eGo I3 Iteration 17.3.2004

2. T-76.115 Project Review 2 Agenda  Project status (20 min)  achieving the goals of the iteration  project metrics  Used work practices (5 min)  Completed work (15 min)  demo  Plans for the next iteration (5 min)

3. T-76.115 Project Review 3 Status of planned goals of the iteration  Pilot case – Partially OK  The pilot case releaved new feature in quota control that was needed (multiquotas)  After this was solved pilot was started and a new blocker bug was founded(cookies in wap gateway in a long period of time)  The pilot was paused and the bug solved.  Pilot continued later  Working product – OK  Data export – OK

4. T-76.115 Project Review 4 Realization of the tasks  Planning was more accurate than in I2 partly because of shorter period of time  Some hours were left to the last iteration  Meetings took lot less time than expected namedoneplandiffleft *TOTAL*166.50193-26.50.00 DS:Write/update tech. specs9.00100.00 GE:Meetings (customer)9.0021-120.00 GE:Meetings (internal)10.0014-40.00 IM: Bug fixing16.00170.00 IM:Use Case 29.00810.00 IM:Use Case 616.001060.00 IM:Use Case 810.0015-50.00 IM:Use Case 911.50101.50.00 IM:Write user guides12.50102.50.00 PM:Other project management10.0015-50.00 PM:Personal SE practice11.5014-2.50.00 PM:Plan the next iteration3.006-30.00 PM:Project review and preparation14.001400.00 PM:Write progress report3.006-30.00 TE:Execute and report peer tests7.0080.00 TE:Execute and report tests15.001500.00

5. T-76.115 Project Review 5 Working hours  About 90% of project is done  Only 130 hours left  Group had lot of other tasks collapsing with software project  Work was done in few long sessions  The ”Big Picture” shows that allthough some differencies between persons in iterations the sum of all work is still tolerable

6. T-76.115 Project Review 6 Quality metrics  BugZilla is part of our everyday life  Most of the open bugs are from peer testing I1I2I3DETotal Reported 13201750 Closed 1318839 Open 02911 Bug metrics BlockersCriticalMajorMinorEnhancementTotal Total open 0029011 This iteration reported 000909

7. T-76.115 Project Review 7 Quality assessment  Feedback from the Quality Department  Peer testing  Pilot project  System testing at the end of iteration  Overall state of the system is good  Additional bug reporting tools used: TODO-lists, email, Messenger, ICQ...  Overall quality is good Functional areaCoverageQualityComments Web UI3 Thoroughly tested Questionnaire tool2 In good shape Screening with WAP2  Test more! 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

8. T-76.115 Project Review 8 Test Documentation  Test planning  System test plan plus separate plan for peer group  Test cases  Used same verified practices as before  Test specification includes test log  Test report  concludes the results of testing  report from peer testing was also delivered  QA in the future  system testing in cooperation with customer  continue research on compatibility with different phone models

9. T-76.115 Project Review 9 Peer testing  Peer testing was executed by group Muuntaja  user manuals (web, wap)  questionnaire upload  web UI functionalities  wap interviewing  Valuable feedback  practical problems (login etc.)  problems with WinWAP emulator  8 bugs reported in Bugzilla (severity unspecified)  Usability was considered good

10. T-76.115 Project Review 10 Software size (Java)  Configuration work, web resources, excel macros etc not included here  VM pages are also not included (both web and wap)  New ways of measuring the code.  The memory space of running project (perhaps some indications of size) Esurvey is 62 Megs at the time.  The number of methods 376 and the number of classes 61  Hours spend on coding (this only works if same team in different projects) 481 hours PPI1I2I3DE Lines of Code in Methods (LOCm) 0368722799 Number of statements (NOS) 0261572657 Number of Lines 0285968387095

11. T-76.115 Project Review 11 Risks  Risk management is done by three the members of the group attending risk management module  Risk management plan is documented and updated as part of project plan  Current top-5 risks and their countermeasures:  Decrease of motivation caused by too much work in proportion to credits  workload balancing  Hacker attack on server  Distribute code base into group members’ homes  Binary upload of questionnaire  research  Customer requirements not fulfilled  meetings, pilot project...  Interviewing doesn’t work on some important phone model  Use friends’ phones for testing!

12. T-76.115 Project Review 12 Work practices  The group has used all the mandatory practices demanded by the course  Trapoli has not been working reliable. Crashes on every delivery  Bugzilla has been used extensively  The software has been builded in cycles  Personal practice reports are almost ready  Personal practice ”Communication practices” for a closer look  Communication method has to be decided according to target  Different methods with different stake holders  If method is used too much it looses its power

13. T-76.115 Project Review 13 Results of the iteration  DEMOTIME

14. T-76.115 Project Review 14 Plan for the next iteration  Goals  Finish the course with good grade  Leave customer satisfied  Deliverables  Code and deployable packets on a CD  Printed manuals  Final report  Final versions of all documents DS:Write/update Documents20ALL19.3.20047.4.2004 GE:Meetings/Training(customer)14lheleniu19.3.20047.4.2004 GE:Meetings (internal)7lheleniu19.3.20047.4.2004 GE:Meetings (status/mentor)7lheleniu19.3.20047.4.2004 IM: Bug fixing20ALL19.3.20041.4.2004 PM:Other project management10lheleniu19.3.20047.4.2004 PM:Personal SE practice7ALL19.3.20047.4.2004 PM:Project review and preparation10lheleniu1.4.20047.4.2004 PM:Write progress report4lheleniu1.4.20047.4.2004 TE: General Testing5jjkoivul19.3.20041.4.2004