T-76.115 Project Review

1. TeXlipse [PP] Iteration3.11.2004 T-76.115 Project Review

2. Agenda Introduction to the project Project status (10min) Status of the iteration's goals Status of the iteration's deliverables Realization of the tasks Working hours per person Risks Work results (20 min) Results of the iteration Project plan (No working demo can be presented at the moment.) Used work practices (5 min) Chosen common work practices. SEPAs

3. Introduction to the project The customer has a constant need for the creation of LaTeX documents. The Eclipse IDE is free, powerful and gaining in popularity and it offers a rich environment for extension through a plugin architecture. There are existing free plugins for this, e.g. the ecleTeX -project, but they are lacking in features. The general purpose of this project is to create a LaTeX plugin for Eclipse IDE. The developed plugin, TeXlipse, is to provide a efficient developing environment for creating LaTeX-documents. Some of the key features to achieve this include: Syntax highlighting Folding Templates Build support Keyboard shortcuts Support for several platforms

4. Status of the iteration’s goals Forming a group and learning to know each other OK, a group has been formed and meetings have been arranged together. Dividing roles and responsibilities Each group member has an individual responsibility. Agreeing on basic issues like for example communications channels The basic communications channel is TikiWiki and IRC. The group will participate on the T-76.633 course concerning communication. Agreeing on primarily used programs Eclipse was naturally chosen to be the primary development tool. CVS is used for version management. Choosing and presenting SEPA topics Will be discussed later in this review. Project planning and schedule familiarizing Trapoli is used for effort tracking. Understanding the product to be delivered The requirements were quite clearly expressed by the customer. Identifying and analyzing the project risks No big risks have been identified yet.

5. Status of the iteration’s deliverables Project Plan OK, Some chapters will be updated during the project. Effort estimations and plans Practices Requirements Schedule Risk log Requirements document OK, Must still be approved by the customer. Use cases implemented and tested Some use cases have been addressed in the requirements document. No use cases have been implemented yet.

6. Realization of the tasks • Some more effort was estimated than was in reality committed. • It was really difficult to estimate the required time for studying the different domains. • Finding a group and starting the project was easier than expected.

7. Working hours by person Planned hours for the total project Realized hours in this iteration

8. Quality metrics No real quality control has been implemented yet. This was the Planning iteration

9. Quality assessment No real quality control has been implemented yet. This was the Planning iteration

10. Software size in Lines of Code (LOC) No software has been developed yet. This was the Planning iteration

11. Changes to the project The project has not been changed from a previously agreed one. This was just the first iteration of the project. No previous agreement.

12. Risks Current situation regarding the risks No risks have materialized yet. Some riks have been identified: The mostly used communications channels are network dependent. No access to the network on a crucial time. Information is not delivered to everybody. Keep the phone numbers of group members available. Version management is done on CVS. CVS breaks down. Most project files are lost. Keep local copies of the files. The software to be developed is a plugin for existing software. Some aspect turns out to be very difficult to implement. Effort estimates are wrong, time consumption increases. Study the underlying technology well in advance. The requirements were mostly given by the customer. A requirement turns out to be difficult or impossible to implement. All features cannot be implemented. Study the requirements and prioritize them.

13. Results of the iteration The most important substance of the major deliverables of the iteration: project plan requirements system architecture QA approach Demonstrate the developed software Unfortunately no demo can be presented at the moment, because the system has not been programmed yet.

14. Project plan (1/3) Stakeholders and staffing The project stakeholders can be divided into three general categories. The project group takes care of the system development. The customer and his technical advisors act together as the principal. The mentor's role is inbetween these two parties taking care that all the requirements set by the course are taken care of and that the project is proceeding as planned. The System Architect has an especially important role, as he gives technical support for the Project Manager and is thus involved with for example the customer meetings.

15. Project plan (2/3) • Project goals • Delivery of a high quality tool • Easy and effcient usage, positive user feedback • Satisfied customer • Meeting the requirements • Passing the course with a good grade • The received grade • Smooth operation of the group • Everybody happy • Effcient usage of resources • Tracking effort, staying within budgeted time • Even workload for all group members • Everybody doing their share • Fun co-working • Positive feelings after the course

16. Project plan (3/3) • Project practices and tools • Static methods (by Esa and Oskar) • Pair programming (by Laura and Taavi) • Design Patterns (by Antti and Kimmo) • Communication practices (by Jani)

17. Used work practices Experiences of used practices mandatory practices: time reporting with Trapoli Trapoli seems a bit unefficient The group has now agreed to do the reporting directly after the task. SEPAs The communication practices SEPA has already proven usefull. The other SEPAs will be adopted later in the project.