Beruflich Dokumente
Kultur Dokumente
University of Tampere, Department of Computer Sciences University of Tampere, Department of Computer Sciences University of Tampere, Department of Computer Sciences University of Tampere, Department of Computer Sciences
Requirements Engineering
Lecture 4 Product vision and project scope
Zheying Zhang Department of Computer Sciences University of Tampere
Understand the importance of good project scope management Explain the project scope management process and techniques used at each stage Prepare for project scope and vision document
Basic concepts
University of Tampere, Department of Computer Sciences
Product vision
Captures the essence of the product Serves as the basis for discussion and agreement among the primary internal stakeholder communities
The marketing and product management team proxy for customers and users The project team product development The management team business outcome of the endeavor
Scope
Work content of a project Activities
Project scope
University of Tampere, Department of Computer Sciences
Scope
Pertains to a specific project Be more dynamic than vision Project managers adjust the contents of each release Can appear in project requirements document
Business requirements
Determine the business tasks and the application enables Influence the implementation priorities for business tasks and their associated functional requirements Influence the way requirements are implemented
Business requirements collected from multiple sources might conflict. Project sponsor is responsible to solve the conflicts Baseline is the itemized set of features intended to be delivered in a specific version of the application
acceptable to the customer reasonable probability of success
7
The project team and stakeholders must have the same understanding of what products will be produces as a result of a project and what processes will be used in producing them Without an agreed upon and documented vision, there is little ho pe of achieving success
Management or marketing: view possibly come from customer Architects and designers: possibly with no customer contacts (mull over or modify the vision for what is feasible) Developers: take off with their own vision Customers: may have a whole new expectation
A major reason for project failure is the failure to spend the time at the beginning of the project on clearly defining the project scope and define the project requirements before beginning product development
9
10
Scope Initiation
New project or commitment to next phase of existing project Inputs:
Product vision / business need Strategic plan / goals Project selection criteria and methods Expert judgment, historical information
Initiation: beginning a project or continuing to the next phase commitment to next phase Scope planning: developing documents to provide the basis for future project decisions written scope and vision statement Scope definition: subdividing the major project deliverables into smaller, more manageable components - WBS Scope verification: formalizing acceptance of the project scope formal acceptance Scope change control: controlling changes to project scope
11
12
Why are we doing this? Describes the needs of typical customers or of the target market segment Need typically initiates a project
e.g. a market demand, a business need, a customer request, a technological advance, or a legal requirement
We need a company web page We have to increase exposure to customers We have to improve internal company communications
14
Business risks
University of Tampere, Department of Computer Sciences
Summarize the major business risks associated with developing or not development of the system
Marketplace competition Timing issues User acceptance Implementation issues Possible negative impacts on the business
15
16
There are usually more projects than available time and resources to implement them Methods include
focusing on broad organizational needs categorizing projects financial analysis weighted scoring model Balanced scorecard
Low Benefit
High Benefit
17
18
Project charter
After deciding what project to work on, it is important to formalize projects A project charter is a document that formally recognizes the existence of a project and provides direction on the projects objectives and management Key project stakeholders should sign a project charter to acknowledge agreement on the need and intent of the project
Assumptions
20
Project charter
University of Tampere, Department of Computer Sciences University of Tampere, Department of Computer Sciences University of Tampere, Department of Computer Sciences
Formalizes existence of project Provides direction on objectives Signoff by key project stakeholders
Charter Components:
Title, date Project manager Project objective Summary of approach Roles and responsibilities matrix Sign-off Comments (assumptions, constraints)
21
22
Scope planning
Scope planning
The process of developing a written scope statement as the basis for future project decisions The scope statement forms the basis for an agreement between the project team and the project customer by identifying both th e project objectives and the major project deliverables
Steve McCann
Director of Purchasing
Sign-off: (Signatures of all above stakeholders) Comments: (Handwritten comments from above stakeholders, if applicable) This project must be done within ten months at the absolute latest. Mike Zwack, CIO We are assuming that adequate staff will be available and committed to supporting this project. Some work must be done after hours to avoid work disruptions, and overtime will be provided. Jeff Johnson and Kim Nguyen, Information Technology Department
23
24
A scope statement is a document used to develop and confirm a common understanding of the project scope. It should include
a project justification a brief description of the projects products a summary of all project deliverables a statement of what determines project success
Business context
Stakeholder profiles Project priorities Operating environment
26
25
Example: Online Book Selling System (OBSS) Business opportunities: growing demand of online shopping business BO-1: increase book sale by 20% per year BO-2: Reduce order handling time by 20% within 3 months following initial release in comparison with earlier order handling per day
27
Feature FE-1: View book catalog FE-2: Order books FE-3: Track and manage pervious orders and update account information FE-4: Register for b o o k payment options FE-5: Request book delivery FE-6: Book management FE-7: Customer management FE-8: Discuss contents of books in a forum and give ratings on comic books
Feature Release 1 FE-1 FE-2 FE-3 FE-4 FE-5 FE-6 FE-7 FE -8 Fully implemented Sends order requests via email to store Customers see 3 latest orders Cash on delivery Books will be delivered onsite Create, view, modify, and delete book items Register for an account Not implemented
Release 2
Fully implemented Fully implemented Fully implemented Add delivery from bookstore to selected offsite locations Fully implemented Fully implemented Fully implemented
30
29
Different points of view from different stakeholders Identifying stakeholders often simply involves interviewing decision makers, potential users, and other interested parties
Who are the users of the system? book shoppers who is the customer (economic buyer) for the system? bookstore (managers) Who else will be affected by the outputs the system produces? store staff, book shoppers Who will evaluate and approve the system when it is delivered and deployed? product managers, store managers, sponsors Are there any other internal or external users? publishers, product developers Who will maintain the new system? store technical staff Is there anyone else who cares? store corperators What are the existing systems that will interact with the system? Red Hat Linux and Apache HTTP Server
31
Stakeholder
Major value
Attitudes
Major interests
Constrains
Book increased sales; receptive but Minimal new store marketing exposure cautious technology needed; managers to generatenew concern about customers resources and costs of delivering books Bookstore more efficient use of receptive job preservation staff staff time throughout the day; higher customer satisfaction Book shopper Easing book search, Strong reviewing, and enthusiasm purchase
training for staff in Internet usage needed; delivery staff and vehicles needed
32
Scope definition
University of Tampere, Department of Computer Sciences
33
34
36
1.0 Concept 1.1 Evaluate current systems 1.2 Define Requirements 1.2.1 Define user requirements 1.2.2 Define content requirements 1.2.3 Define system requirements 1.2.4 Define server owner requirements 1.3 Define specific functionality 1.4 Define risks and risk management approach 1.5 Develop project plan 1.6 Brief web development team 2.0 Web Site Design 3.0 Web Site Development 4.0 Roll Out 5.0 Support
37
38
Use formal templates if available The analogy approach: It often helps to review WBSs of similar projects The top-down approach:
Start with the largest items of the project and keep breaking them down iteratively add levels of detail
Combination
39
Scope verification
University of Tampere, Department of Computer Sciences
Scope change
Scope Change Control is concerned with:
Factors that create scope changes to ensure that changes are agreed upon Determining that scope change has occurred Managing changes when they occur
Inspection/reviewing Outputs:
documented level of completion documented acceptance
41
42
43
44