1 / 11

T-76.4115 Iteration Demo

T-76.4115 Iteration Demo. CloudSizzle PP Iteration 21.10.2009. 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). Agenda.

yakov
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 CloudSizzle PP Iteration21.10.2009

  2. 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) Agenda This template contains the minimum set of topics for the review. This slide set should also serve as the progress report. It may and should contain slides with additional details, that you don’t even intend to show due to limited time allocated for the presentation

  3. Introduction to the project • What • A social study planner • students can create a study plan, share it to their friends • Students can enroll to courses, invite friends to courses • Students can utilize the social networks to collaborate • Students talk about course related matters in discussion channels • Why? • to get an understanding of the Smart-M3 RDF store • to get an understanding of how it can be used to enable interoperability between OtaSizzle services and third party services. • To demonstrate how information can be extracted from Noppa and Oodi through loose coupling

  4. Status of the iteration’s goals • Project initialization • NOT OK. Development environment/tools should be set up • OK. Development and project tools should be used by everyone in the team • OK. Communications should work inside the team and to the customer • NOT OK. Divide the tasks inside the team • NOT OK. Identify risks during PP iteration • Requirements elicitation • OK. Find out all stakeholders requirements for the project to a suitable detail • LATER. Create use cases • OK. Prioritize the requirements • OK. Requirements meeting with customer • The team should learn the technologies used for the implementation • OK. Workshop to teach the technologies and software • Premilinary architecture planning • OK. Choose the implementation language • OK. Get a high level view on software architecture • Getting to know the team and the stakeholders • NOT OK. Kick-off meeting to break the ice

  5. Status of the iteration’s deliverables • Project plan • OK, except chapter 1.3, because … • Requirements document • OK, all important requirements documented in general level and reqs 1,2,3,... in detail

  6. Realization of the tasks • Show status and effort distribution per task or task group • (not on too detailed level) • discuss major discrepancies between the plan and realizations • unfinished/removed tasks? • any unplanned tasks? (A sample table) * unplanned task (= a new task added during the iteration)

  7. Resource usage Original plan (in the beginning of the iteration) • Underspending (40%) with respect to the estimates. The main reason being a too optimistic view at estimation time about the ramp-up phase. • All underspent hours were distributed evenly among remaining iteratons. Realization and updated plan (realized hours and updates)

  8. Risks • What is the current situation regarding the risks? • materialized risks? • new risks identified?

  9. Results of the iteration • Briefly describe the most important content of the major deliverables of the iteration, e.g., the following • project plan (especially in PP review) • requirements (especially in PP review) • system architecture (especially in I1 review) • QA plan (especially in I1 review) • implemented use cases (I1-I2) • user’s manual (I2) • Demonstrate the developed software • first tell briefly to the audience what you are going to demonstrate • distributing a demo script to the audience helps following the demo • concentrate on new functionality Avoid repeating what you have already told in project status and concentrate on showing the concrete results.

  10. Example: Project plan • Present the following • Stakeholders and staffing (a diagram?) • Project goals (discuss most important goals and verification criteria) • Project resources (already shown in the project status?) • Project practices and tools (discuss most important practices and tools you have chosen, what, why, when, …) • Discuss phasing if there are some major plans already

  11. Used work practices • How have you been using the planned work practices, what are the experiences of • mandatory practices: time reporting, version control, … • any other practices • Are you going to • adopt some new practices • change the use of the current practices • stop using some adopted practices In the presentation you have time to discuss only the most interesting experiences and major changes. The mentor will read the rest of the material from the slides himself later.

More Related