T Iteration Demo Tikkaajat [PP] Iteration

T Iteration demo 2 Agenda  Project status (10-15 min)  achieving the goals of the iteration  project metrics  Work results (20-25 min)  presenting the iteration’s results  Used work practices (5 min)

T Iteration demo 3 Introduction to the project  jEhIntranet System  Informational logistic solution for Eduhouse Oy  coordinating system for customers, employees, and operations

T Iteration demo 4 Introduction to the project  jEhIntranet System  Current system allready exist  Extended over time  Overlapping  Cluttered code  Low speed functionality  Lack of documentation  The basic idea is to re-develop the current system as ready as possible  Using Java language and different techniques  Hibernate, Velocity, Ajax  Documentation for furher development

T Iteration demo 5 Status of the iteration’s goals  Goal 1:Project planning  OK  Goal 2: Understanding the domain  OK  Goal 3: Requirements specification on general level including most important functional requirements and use cases  OK  Goal 4: Selecting appropriate tools  OK  Goal 5: Setting up the development environment  OK  Goal 6: Defining working practices  OK  Goal 7: Training in the development environment  OK  Goal 8: Preliminary database description  OK  Goal 9: Preliminary architecture  OK

T Iteration demo 6 Status of the iteration’s deliverables  Project plan  OK, except chapter 5.2, because quality assurance plan will be separated document delivered 2.11  Requirements document  OK, all important requirements documented in general level  SEPA diaries (at least ch. 1)  OK  Instructions and guidelines for development (communication, coding, reporting)  OK  Preliminary database description document  OK  Preliminary architecture document  OK

T Iteration demo 7 Realization of the tasks Status RealizedPlanned Diff(Left) Project PlanningOk Task 1. Planning and decision makingOk24, ,526,5 Task 2. DocumentationOk25,522+3,5 Requirements EngineeringOk Task 3. Elicitation, analysis, priorization, validation Ok18,528-9,59,5 Task 4. DocumentationOk TrainingOk Preliminary database descriptionOk17,521-3,53,5 Preliminary Architecture description MeetingsOk ManagementOk Task 5. Project trackingOk63+3 Task 6. ArrangementsOk19,58+11,5 Unclassified tasksOk42,575-32,532,5 SEPA Task 1 Pair Programming (ch 1) Task 2. Automated Unit Testing (ch 1) Total

T Iteration demo 8 Resource usage TLTHSMVSSTVHTMTIYZSUM PP I I Total Original plan (in the beginning of the iteration) Realization and updated plan (realized hours and updates) TLTHSMVSSTVHTMTIYZSUM PP 7173,556, I1 7675,547, I Total

T Iteration demo 9 Risks  Top-level risks (of total 16)

T Iteration demo 10 Results of the iteration  Project plan  Project plan document  Requirements  User requirements document  Preliminary system architecture  Preliminary architecture  Preliminary database description

T Iteration demo 11 Project plan  Stakeholders and staffing  Project goals  Project resources (hardware and budget)  Project practices and tools  Phasing

T Iteration demo 12 Project Plan  Stakeholders

T Iteration demo 13 Project Plan  Project goals  Database of the current system needs to be improved and implemented entirely (Prior 1)  Improved means that the DB is more uniform  Implemented means that the DB is designed, implemented and tested  All needed data is in the implemented DB  Queries has to be at least as fast as current DB is  Software engine has to be maintainable and expandable and some functionality from the current system has to be implemented (Prior 2)  Core functionality for the personnel and trainers  Verification against test cases and guidelines  Improved graphical user interface has to be implemented for the implemented engine parts (Prior 3)  Verification against test cases

T Iteration demo 14 Project Plan  Project resources  Hardware  One server from the customer  Personal Computers used in the development  Budget  Salary for team members 20€/h, for mentor and technical expert 30€/h

T Iteration demo 15 Project Plan – practices and tools  Practices  1) Iterative development and planning  Iteration planning in the end of last iteration  Goals, deliverables – customer validation  Sprint planning in the end of last sprint  Tasks are frozen during sprints

T Iteration demo 16 Project Plan – practices and tools  Practices  2) Risk management  Identify  Stakeholders involved  Brainstorming  Analyzing  Probability  Impact  Controlling actions  Avoid or reduce the effect of risk  Monitoring  Risk situation  Status of controlling actions  Constantly monitored  Documentation updated when needed

T Iteration demo 17 Project Plan – practices and tools  Practices  3) Communication  Cell phone - critical information  - important information  IRC - realtime communication  Weekly meetings – ensures that relevant information reaches all partisipants  MediaWiki - all public documentation (guidelines, minutes, etc.) reachable

T Iteration demo 18 Project Plan – practices and tools  Practices  4) Defect tracking  Found defects are reported, unless they are immediately repairable  Defects are prioritized and they are ranked by impact value  Defects are given for fixing to developers according to impact value  Fixed defect is reported  5) Time tracking  Weekly reporting and tracking  Software tool used for reporting  6) Documentation  Against templates  Same format (deliverables in PDF, others in DOC)  7) Coding conventions  Specific guidelines published in MediaWiki

T Iteration demo 19 Project Plan – practices and tools  Tools  1) Management  MediaWiki, used for group presentation, communication and some document preparation  Bugzilla, maybe used for issue tracking  Weekly reporting tool, used for reporting working hours for status tracking and other project management tasks. Implemented by project manager and running on his server.  MS Office programs (Excell, Word, PowerPoint)  2) Development  Eclipse, used as integrated development environment  Ant, used as build tool for the project  Subversion, used as version controlling tool

T Iteration demo 20 Project Plan - Phasing jEhIntranet 1550 h 1. Iteration (3 weeks) 447 h (realized) Iteration plan Project plan Requirements engineering Training Documentation Architecture Management 2. Iteration (7 weeks) 603 h (planned) Iteration plan Architecture Implementation Quality assurance Documentation Management Requirements engineering 3. Iteration (7 weeks) 500 h (planned) Iteration plan Implementation Quality assurance Finalization Documentation Test reports Peer testing Management

T Iteration demo 21 Requirements  Business goals  Main domain concepts  User groups  Functional and non-functional requirements

T Iteration demo 22 Requirements – business goals  Current system is very complex  Further development almost impossible  Very risky to add new features Solution Reconstruct the whole system  Expandable  More easier to modify  More uniform

T Iteration demo 23 Requirements – main domain concepts

T Iteration demo 24 Requirements – user groups

T Iteration demo 25 Requirements functional and non-functional requirements  Most important functional 1. User can login to system 2. User can logout from system 3. Personnel can add courses 4. Personnel can add customers 5. Persinnel can see upcoming courses using the calendar  Most important non-functional requirements 1. Database is uniform 2. System is modifiable 3. System is extendable 4. Only registered users are allowed to use the system 5. Personnel may have different priviledges

T Iteration demo 26 Used work practices  How have you been using the planned work practices, what are the experiences of  Project tracking is more time consuming than predicted  More resources to the development in the viewpoint of quality.  Prototyping teached us  Coding conventions  Testing  Pair-programming is effective way to implement modules and to share experiences  Schedule is hard to fit to serve all participants  Weekly meetings are a good way to share information  Weekly reporting  Reporting needs to be focused to planned tasks  Too detailed tasks?  Frustrating if slacks in reporting  tracking needs to be done multiple times  Version control  Guidelines needs to be defined  Data-losses  new risk identified  Process improvements  Adopting Skype in the upcoming iteration?