1 / 56

The Startup Stage

Requirements Eng. & Project Manag. The Startup Stage. Jerzy Nawrocki Jerzy.Nawrocki@put.poznan.pl. Organizational issues. Lectures: Tuesday , 15:15 , room 144, Lecturing Center? Duty hours: Friday , 14:00 – 15:00 , room 109, Lecturing Center. Get-together Micro Party. Agenda.

jthigpen
Download Presentation

The Startup Stage

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. Requirements Eng. & Project Manag. The Startup Stage Jerzy Nawrocki Jerzy.Nawrocki@put.poznan.pl

  2. Organizational issues Lectures: Tuesday, 15:15, room 144, Lecturing Center? Duty hours: Friday, 14:00 – 15:00, room 109, Lecturing Center

  3. Get-together Micro Party

  4. Agenda • Aim and scope of the stage • Business value of the project • Technical and organizational considerations • Risk management at the Startup stage • Closing the stage

  5. Agenda • Aim and scope of the stage • Business value of the project • Technical and organizational considerations • Risk management at the Startup stage • Closing the stage

  6. Agility Alliance Manifesto O K Individuals and interactions Working software Tommorow or never! Customer collaboration Responding to change

  7. O K Individuals and interactions Working software Tommorow or never! Customer collaboration Responding to change The Fifth Principle of Agility Solved problems over advanced software

  8. XPrince Lifecycle

  9. XPrince Lifecycle

  10. XPrince Lifecycle

  11. XPrince Lifecycle

  12. Do we need anything else?

  13. Do we need anything else? People spend too much time on thinking how to run a project and too little on if the project is worth running. Tim Lister The Atlantic Systems Guild Inc.

  14. Project Sieve Metaphor Project C Project A Project E Project B Project D

  15. Project Sieve Metaphor Project C Project A Project E Project B Project D Project sieve

  16. Project Sieve Metaphor Project C Project sieve Project A Project E Project B To be planned Project D

  17. Project Sieve Metaphor Project sieve = Company’s strategy

  18. How to get the best strategy? Michel Robert, The New Strategic Thinking. Pure and Simple. Michel Rober, Nowe myślenie strategiczne. Czyste i proste, MT Biznes, Warszawa, 2006.

  19. XPrince Lifecycle ?

  20. Main outcomes of Initiation Business Process Reengineering Non-functional requirements Roles (Actors) Outline of functional requirements Outline of the architecture . . . Initiation

  21. XPrince Lifecycle ?

  22. XPrince Lifecycle and SDS

  23. Aim of the Startup Stage • Answering two questions: • What is business motivation for the project? • Is it worth to invest in project planning?

  24. Non-functional requirements for Startup The Startup stage should be as short and cheap as possible.

  25. Agenda • Aim and scope of the stage • Business value of the project • Technical and organizational considerations • Risk management at the Startup stage • Closing the stage

  26. Project’s value Project’s value = Problem’s value

  27. Approach to planning Sharpen the saw Seek first to understand, Synergize then think about money and time Seek first to understand Think win/win Put first things first Begin with the end in mind Be proactive 7 Habits of Highly Effective People

  28. Initial Business Case 1 Context Who is the customer? 2 Problems and Their Impact 3 Outline of the Solution 4 Business Constraints Budget

  29. Context Poznan University of Technology 9 faculties ~ 19 000 students ~ 2 000 employees • Studies: • Undergraduate and Masters • Postgraduate • Ph.D. studies www.put.poznan.pl Campus Piotrowo

  30. Problem About 5000 – 7000 candidates a year. FCM 2006: 1 300 candidates (full-time) I’ve brought the documents I’ve brought the certificate Results Enrollement Enrollement Disadvantage: It’s time consuming

  31. Outline of the solution Let’s send by Internet. I’ve brought the certificate Results Enrollement • Advantages: • A candidate comes just once. • Come only those who have been accepted (less work).

  32. Constraints • The due date is 15 June, 2008 (enrollment process starts in the end of June)

  33. Agenda • Aim and scope of the stage • Business value of the project • Technical and organizational considerations • Risk management at the Startup stage • Closing the stage

  34. Further questions How?

  35. Context diagram Wydział Architektury Wydział Budownictwa i Inżynierii Środowiska Wydział Budowy Maszyn i Zarządzania BANK Wydział Elektroniki i Telekomunikacji Sokrates ? Wydział Elektryczny Wydział Fizyki Technicznej Wydział Informatyki i Zarządzania Wydział Maszyn Roboczych i Transportu Candidate Wydział Technologii Chemicznej

  36. Context diagram Bank Socrates 1 Socrates 2 System Candidate Socrates 9

  37. Optional approaches External system Internal system Solution From University of Lodz Extended version of the Xanthippe system developed at PUT

  38. Optional approaches External system Internal system Many systems Solution

  39. Context diagram Bank Socrates 1 System 1 System 2 Socrates 2 Candidate System 9 Socrates 9

  40. Optional approaches External system Internal system One system Many systems Solution

  41. Context diagram Bank Socrates 1 Socrates 2 System Candidate Socrates 9

  42. Optional approaches External system Internal system One system Many systems Solution

  43. Additional constraints • Communication with the Socrates systems. • No modifications of Socrates are possible.

  44. Quality criteria • No delay • Reliability • Data security • Usability

  45. Further questions .. and by whom?

  46. Project Board Senior User Executive Główny dostawca Project Manager Architect Analyst Kierownik Zespołu Kierownik Zespołu Developers XPrince Team Prince2 XP

  47. Agenda • Aim and scope of the stage • Business value of the project • Technical and organizational considerations • Risk management at the Startup stage • Closing the stage

  48. Risk management Preparation Fighting • Identification • Evaluation • Planning • Monitoring • Avoiding • Reacting to contingency

  49. Business risk factors EPIC E = business Environment impacting the project, P = Problem to be solved, I = Investor willing to pay for solving the problem, C = business Constraints imposed on the project,

More Related