1. T-76.4115 Iteration Demo LicenseChecker I2 Iteration 03.03.2009

2. T-76.4115 Iteration demo Agenda  Project recap (5 min) ‏  Project status (x min) ‏  achieving the goals of the iteration  project metrics  Work results (x min) ‏  presenting the iteration’s results  demo  Used work practices (x min) ‏

3. T-76.4115 Iteration demo Introduction to the project  This project was about continuing development of already existing tool  Opening connections to Open Source Community  To get someone continue the development of the tool when the course ends  Adding new features  More usability  More functionality  Better looks  More support for different programming languages  Making the tool Open Source compatible  In short making the tool better

4. T-76.4115 Iteration demo Project recap 1/2  Project Planning  Some problems  Some changes in team roles  Regardless of all problems results were good  Excellent as a learning experience  Motivated the team and grew the fellowship  Was a booster to merge the team as one

5. T-76.4115 Iteration demo Project recap 2/2  Iteration 1  Groups first real iteration  Moved the development from SourceForge to OW2  Work started well and progress was made  Work was divided more equally  Some errors were made with allocating time for testing  The PM gave a presentation in Paris about OSLC  Good feedback and a lot of interest  In all good iteration  Opened up connections to OS community  New features  Support for SVN & CVS  Copyright check  GUI to add new licenses  List compatible licenses  Localization  Support fot Javascript  Installer  Report export as PDF or RTF

6. T-76.4115 Iteration demo Results of the last iteration

7. T-76.4115 Iteration demo Status of the iteration’s goals  Keeping the team functioning properly  No conflicts, everyone was motived, excellent team spirit  Following and refining the defined practices  Defined practices were followed, testing was done earlier  Observing the used hours more carefully  Team members were noticed if demanded hours were not achieved  Achieving, or if necessary slightly exceeding the budgeted hours  Implementing all tasks assigned  All tasks were finished and implemented  Delivering a working system without any critical bugs and more features  Continue opening connections to the Open Source Community  New developers, merged code and outsource a feature

8. T-76.4115 Iteration demo Status of the iteration’s deliverables  Use cases  Manual  Small manual with the product and more through in Wiki  Final product  Released in OW2  Updated PP  Updated RE Document  Updated Technical Specification  Test Cases  Peer test session charters with exploration logs   QA Report  Test Log  Final Report  Progress Report

9. T-76.4115 Iteration demo Status of iterations features  List compatible licenses  Edit license compatibility conditions  Database reconstruction  Download database  Done, tested  Support other scripting languages  Add Creative Commons licenses  Better C library support  Better support for Linux-kernel  This was memory issue  Improve license recognition  Done  Standardized license notation  Enhance GUI  Done

10. T-76.4115 Iteration demo Realization of the tasks

11. T-76.4115 Iteration demo Realization of the features Feature Name F4 List compatible licenses F5 Edit license compatibility conditions F7 Database reconstruction F8 Download database N4 Support other scripting languages N5 Add Creative Commons licenses N6 Better C library support N7 Better support for Linux-kernel N8 Improve license recognition N10 Standardized license notation N11 Enhance GUI

12. T-76.4115 Iteration demo Resource usage Original plan (in the beginning of the iteration)‏ Realization

13. T-76.4115 Iteration demo Defects and other quality metrics  Description of blocker and critical bugs found and open  Other QA metrics  performance analysis metrics  usability test results  source code metrics ... Use this template or make a more detailed table/graph, where you show per module bugs, and/or classifications per criticality, origin (own system testing, code reviews, customer, peer group) etc. 4519151010 Reported in Ix 5 20 Major 7425 22 Reported total 27171021 Open TotalTrivialMinorCriticalBlockers

14. T-76.4115 Iteration demo Quality dashboard  Evaluate the quality of the parts of the system  how much effort has been put on QA practices  what is the coverage of testing  what can you say about the quality of a particular part based on your test results and ’gut feeling’ during testing  is the number of reported bugs low because of lack of testing or high because of intensive testing    Quality Only few minor defects found, very efficient implementation. 2File conversions Nothing serious yet1Admin tools 2 critical bugs found during last test round, lots of small problems 3Encoder Not started0GUI editor CommentsConfidencePart of the system Legend Confidence: (use your own scale)‏ Quality: (use your own scale e.g.: 3 = quality is good 2 = not sure 1 = quality is bad

15. T-76.4115 Iteration demo Quality goals  Evaluation of the status of the project's quality goals

16. T-76.4115 Iteration demo Changes to the project  Some additional features

17. T-76.4115 Iteration demo Risks  Time conflicts  Other school projects  Work  Estimation errors for each task in project level and also in personal level  Tasks should been divided into smaller bits  Team member running low on resources  Lack of testing/allocating time for testing  Lack testing skill/ecudation

18. T-76.4115 Iteration demo Used work practices  Team meetings  At least every week  Status checks/progress reports, problem solving, current issues  Code review  One session after team meeting  Everyone joined, was extremely useful  Testing  Done during development (Unit, regression, functional testing) ‏  Major testing (system testing + test case based testing) done at the end of each iteration  Programming sessions  Smaller coding sessions held (at least 2 developers) ‏  Were quite useful

19. T-76.4115 Iteration demo Results of the iteration  Building a community  Development continues  University hiring two part-time developers to continue the project  User manual and other important documents moves OW2 Wiki  More functionality to the tool  Next demo

20. T-76.4115 Iteration demo Example: Demo script  System Administrator  function X  function Y  …  Basic user  function Z1  function Z2  …