T Project Review X-tremeIT I1 Iteration

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 2 Agenda  Project status (x min)  achieving the goals of the iteration  project metrics  Used work practices (x min)  Completed work (x min)  presenting the iteration’s results  demo  Plans for the next iteration (5 min)

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 3 Status of planned goals of the iteration  Ratification of the requirements  Designing core architecture of the system  Choosing technologies to use  Designing most important modules & use cases  Writing specifications  Implementing most important modules and use cases on general level  Testing the baseline architecture of the system  Writing test plan  Implementing testing  Reviews  Inspections

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 4 Status of planned deliverables of the iteration  Deliverables:  Implemented use cases/core architectural parts:  Case UC-01: Creating new process diagram  Case UC-02: Add new object  Case UC-03: Add dependency between 2 objects  Documents:  updated project plan  updated requirements document  tech. specification on a general level  test case specifications

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 5 Realization of the tasks

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 6 Working hours by person RealPlanDiff Valeria 62,551,311,2 Aleksandr 52,545,37,2 Vladislav 5545,39,7 Konstantin 5648,37,7 Olesia 50,545,35,2 Roman 64,545,319,2 Seppo 40,145,3-5,2 Total ,155 Realized hours in this iterationPlan in the beginning of this iteration PPI1 Subtot al I2I3DETotal Valeria 6262,5124, Aleksandr 5652,5108, Vladislav 5355, Konstantin Olesia 4150,591, Roman 5064,5114, Seppo 4640,186, Total

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 7 Quality metrics I1I2I3DETotal Reported 00 Closed 00 Bug metrics

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 8 Quality assessment  Evaluate the quality of the different functional areas of the system  how much effort has been put on test execution  what is the coverage of testing  what can you say about the quality of the particular component 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  Assess the quality status of the system against the goals of the iteration Functional areaCoverageQualityComments Communications3 No defects GUI0  Not started Engine3  Not started 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

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 9 Software size in Lines of Code (LOC)  Any remarks on this metric?  lots of new functinality was implemented  refactoring reduced LOC PPI1I2I3DE Total (NCLOC + COM) Comments (COM) PPI1I2I3DE Total – part A Com – part A Total – part B Com – part B Total – part C Com – part C Total Comments … or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 10 Risks  Risk management  Results of risk management practice  New risks

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 11 Work practices  How have you been using the planned work practices, what are the experiences of  mandatory practices: time reporting, version control, …  personal SE assignments  not all in every review, but when there are some interesting findings etc.  other practices  Are you going to  adopt some new practices  change the use of the current practices  stop using some adopted practices

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 12 Example: Test-first approach (N.N.)  Test-first was adopted by 3 coders after short training by N.N.  They used it first for all new code, but later only in modules x,y,z, because …  Metrics  the amount of unit test code is 1000 LOC (20% of total LOC)  80% of test code was written before the real code  effort N.N. spent on preparing the adoption (reading about test-first, planning, training) was 12h  effort the team spent on learning the practice was 7h  Positive experiences  …  Negative experiences  it does not work when xxx because yyy  Overall  the practice seems to be useful  In the next iteration the use of the practice will be slightly changed by adopting the JUnit tool  …

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 13 Results of the iteration  New documents  Technical specifications Technical specifications  Test cases specifications Test cases specifications  Test report Test report  Progress report Progress report  UML class diagram UML class diagram  Other testing related documents  test log test log  Test Cases Matrix Test Cases Matrix  Updated documents  Project plan Project plan  Requirements document Requirements document  Demonstrate the developed software  GUI  Communications

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 14 Plan for the next iteration  Goals:  Integrate system modules  Implement more use cases  Plan and execute tests  Testing approach  Test cases  Continue module testing (GUI)  Integration testing  Deliver the system to the customer  Plan format and content of user manual  Deliveries:  Implemented software  Updated:  project plan  requirements document  technical specification  Test cases  Test report  User’s manual  Progress report

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 15 Plan for the next iteration

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 16 Schedule Week 49Group meetingAll Week 49Customer meeting: Architecture DesignVladislav Week 50iDL Modules integrationOlesia, Konstantin, Aleksandr, Roma Week 50iDL First version of GUI testedRoma Week 3iDL: Implementing more use casesAll Week 3Group meeting / Reviewing Implemented results Week 3Deliver system to customer for possible feedback Week 6iDL : Testing of implemented use casesALL Week 6User manual, final version for I2 phaseSeppo DL: I2 documentation delivery Week 7Project review

T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 17 Thank you! Questions, comments?