1 / 25

T-76.4115 Iteration Demo

T-76.4115 Iteration Demo. Software Trickery PP Iteration 23.10.2007. Project status (10 - 15 min) achieving the goals of the iteration project metrics Work results (10 - 20 min) presenting the iteration’s results Used work practices (5-10 min). Agenda. Introduction to the project .

gypsy
Download Presentation

T-76.4115 Iteration Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.4115 Iteration Demo Software Trickery PP Iteration23.10.2007

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

  3. Introduction to the project • Party management system v2.0 (PMS) • Modular web-based system • Tournament management system module (TMS) • Replaces existing system (non PMS-module) • Extension module for PMS • A solution for managing game tournaments • Main user groups • Administrators • Tournament players • Outside spectators

  4. Status of the iteration’s goals • Goal 1: Creating contacts to all relevant stakeholders • OK • Goal 2: Understanding the problem domain fully • OK • Goal 3: Creating a solution for the given problem • DISCARDED (Practically same as GOAL 2 at this point) • Goal 4: Creating the needed architecture for the project to succeed • MOVED to beginning of I1 • Studied existing PMS architecture • Goal 5: Learning the basic usage of needed technologies for the solution • OK • Goal 6: High level schedule for the project • OK • Goal 7: Identification and preparation for possible risks in I1 • OK

  5. Status of the iteration’s deliverables • Project plan • OK, Except chapter 5.2 (QA Plan) which is to be delivered later (2.11.) • Requirements document • OK, all important requirements documented in general level • Progress report • OK • SEPA diaries • OK • High level Architecture • Moved to Iteration 1

  6. Realization of the tasks * unplanned task (= a new task added during the iteration)

  7. Resource usage Original plan (in the beginning of the iteration) • Individual studying didn’t realize as planned • Architectural design moved to beginning of I1 • Estimating tasks without prior experience was hard Realization and updated plan (realized hours and updates)

  8. Resource usage • Wed and Sun are control points • Estimates upward • Tasks declared done correct the curve • Some members lazy about reporting hours during iteration -> Curve corrects itself during the end

  9. Changes to the project • Major changes since the Iteration plan • Iterations split into two sprints • Developers will be divided into smaller team

  10. Risks

  11. Results of the iteration • Project plan • Project Plan document • Requirements • Requirements document • SEPA diaries • Pyry Lahti and Markus Granström • Topic: Continuous Integration and Automated Testing

  12. Project plan • Stakeholders and staffing • Project goals • Project practices • Tools

  13. Stakeholders and staffing

  14. Project Goals

  15. Project Practices • 1. Iterative development & Iteration planning • 3 Iterations (PP, I1, I2) • 2 Sprints in each implementation iteration

  16. Project Practices • 2. Documenting • Documents created in the customer Wiki for easy availability • Weekly progress reports • 3. Risk management • Identify, evaluate and prepare • 4. Communication • E-mail & IRC • Mailing list • Meetings • Wiki for documents • Phone calls • 5. Defect tracking and version control • Trac provided by the customer • Trac’s svn also used for time tracking (excel sheet)

  17. Project Practices • 6. Coding conventions • C# • PHP • 7. Development & Quality practices • Continuous integration • TDD • Incremental rearchitecture • Peer testing • Developer days (Side-by-side programming)

  18. Project tools

  19. Requirements Engineering • Conceptual model of TMS • Use case diagram • Overall status

  20. Requirements Engineering: Conceptual model of TMS (1/2)

  21. Requirements Engineering: Conceptual model of TMS (2/2)

  22. Requirements Engineering: Use case diagram

  23. Requirements Engineering: Overall status • 8 use case descriptions • 18 functional requirements • 9 non-functional requirements • Still needs to be officially approved • All in all, requirements have been identified and represented quite well. • Good start for I1.

  24. Experiences on work practices • Time reporting is still troublesome • Needs time specific DL (currently only Wed and Sun) • Weekly meetings with customer • Seems to be a good way for sharing knowledge between stakeholders • Individual studying • Needs benchmarking or tasks with deadlines

  25. Any Questions ? • Thank you !

More Related