1 / 30

BTS330

BTS330. Vision & Scope. IT Projects. What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of all IT projects succeed. IT Projects. Why do projects fail? Objectives not fully specified (51%) Poor planning/estimating (48%)

damita
Download Presentation

BTS330

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. BTS330 Vision & Scope

  2. IT Projects • What defines project success? • On time • Within budget • Delivers what the clients want • The reality • Less than 20% of all IT projects succeed

  3. IT Projects • Why do projects fail? • Objectives not fully specified (51%) • Poor planning/estimating (48%) • New technology (45%) • Poor or no project management discipline (42%) • Inadequate skills (42%)

  4. IT Projects • To work towards project success, the team needs to: • Establish a good understanding of the stakeholder community • Demonstrate an understanding of the problem to be solved – have a clear vision and scope for the project

  5. IT Projects • To work towards project success, the team needs to (cont’d): • Capture the real needs of the stakeholders and the system features required to fulfill them • Ensure that the views of the stakeholder community are actively and appropriately represented throughout the project

  6. Stakeholders • A stakeholder is: • An individual who is materially affected by the outcome of the system or the project(s) producing the system *Use Case Modeling by Bittner and Spence, p. 51.

  7. Stakeholder Types • Share the same characteristics and relationships • Users • Actually use the system • Sponsors • Those that have a vested interest in seeing the project succeed. • Funding the project

  8. Stakeholder Types • Developers • Authorities • Experts in a particular aspect of the problem or solution domain • Customers • Those that will be purchasing the final system

  9. Identifying Requirements *Use Case Modeling by Bittner and Spence, Figure 3-3, p. 56.

  10. Identifying Stakeholders • Who are the users of the system? • Who is the sponsor of the development? • Who else will be affected by the outputs that the system produces? • Who will evaluate and sign off on the system when it is delivered and deployed?

  11. Identifying Stakeholders • Are there any other internal or external users of the system whose needs must be addressed? • Are there regulatory bodies or standards organizations to which the system must comply? • Is there anyone else?

  12. Stakeholders • Stakeholders own the problem and are affected by the proposed solution • They are the primary source of the requirements

  13. Gathering Requirements • When to start? • How to start?

  14. Gathering Requirements • Techniques for gathering requirements • Interviews • Questionnaires • Focus Groups • Advisory Boards • Workshops • Reviews • Role Playing

  15. Gathering Requirements • Interviews • Target a small audience • Ask open and closed ended questions • Open ended • Generate discussion • Leads to further questions • i.e. How is a sale processed?

  16. Gathering Requirements • Interviews • Ask open and closed ended questions (cont’d) • Closed ended • Usually a ‘specific’ answer • i.e. How many supplier orders do you generate in a month?

  17. Gathering Requirements • Questionnaires • Can target geographically dispersed stakeholders • Can target a large number at once • Focus Group • Ability to gather specific feedback on specific topics

  18. Gathering Requirements • Advisory Board • Informal focus group • Workshop • Review • Formal or informal meeting to review something specific (i.e. document or prototype)

  19. Gathering Requirements • Role Playing • Used in conjunction with workshops to get feedback

  20. Identifying Requirements • For a project, the team needs to: • know who the stakeholders are • have a shared vision for the project

  21. Vision Statement • Summarizes the long-term purpose and intent of the system • Vision Statement Template: • For (target customer) • Who (statement of the need or opportunity) • The (product name) is a (product category) •  That (key benefit, compelling reason to buy) •  Unlike (primary competitive alternative) •  Our product (statement of primary differentiation)

  22. Vision Statement Sample • Vision Statement Sample for a Chemical Tracking System (MS Software Requirements 2nd edition): • For Jim’s Gym who needs to acquire an automated computer system to run his new business, the Gym Management System is an information system that will provide a single point of access to manage his gym. The system will provide the capability to manage all aspects of Jim’s business such as managing members and fitness staff, schedule employees and fitness classes as well as a gift shop. There will also be services such as massage therapy and private and semi-private instruction with a fitness instructor offered. Unlike the competition, our product will allow members to manage their experience at Jim’s gym through an interactive web interface where customers can sign up for classes and services that the gym will be offering.

  23. Vision Statement Sample • Vision Statement Sample for a Chemical Tracking System (MS Software Requirements 2nd edition): • For scientists who need to request containers of chemicals, the Chemical Tracking System is an information system that will provide a single point of access to the chemical stockroom and to vendors. The system will store the location of every chemical container within the company, the quantity of material remaining in it, and the complete history of each container’s locations and usage. This system will save the company 25% on chemical costs in the first year of use by allowing the company to fully exploit chemicals that are already available within the company, dispose of fewer partially used or expired containers, and use a single standard chemical purchasing process. Unlike the current manual ordering process, our product will generate all reports required to comply with federal and state government regulations that require the reporting of chemical usage, storage, and disposal.

  24. Vision Statement Sample • Vision Statement Sample for a Hockey Stick Manufacturing Company: • ForVitorio, a part owner in Slapshot, who is starting new division named Butterfly to produce specialty goalie sticks for charitable purposes, a software system is needed to manage the production of these goalie sticks. The Butterfly system is a software suite that will manage orders, control and track inventory, secure designs and template, calculate production costs, log orders and track production, maintain shipping and receiving logs, generate invoices. Unlike the current Slapshot system which is not setup to track independent charitable production costs, our product will maintain separate costs, provide accurate costing information and will interface with the existing Slapshot system to maintain an independent business model. This will give Vitorio the information he needs to successfully operate Butterfly.

  25. Vision Statement • Vision statement must provide a sharedunderstanding of the problem to be solved and unify the various stakeholder perspectives

  26. Vision Statement Exercise 1 • For fun: you want to bring a 2nd NHL team to Toronto. Using the Vision Statement Template, write a vision statement to do this. • Who are your stakeholders?

  27. Scope • Represents the features or functionality the system will provide • Features: • Are the high level capabilities of the system • Are necessary to deliver benefits to the users • Fulfill the stakeholders needs • Can be Functional or Non-Functional

  28. Scope • Functional • What will your product provide • i.e. online ordering, managing customer

  29. Scope • Non-Functional: • Performance • Usability • Scalability • Licensing • Installation • Documentation

  30. Scope

More Related