Product Vision & Project Scope By: Bryan Peterson.

Slides:



Advertisements
Similar presentations
Resolving Challenges in Metadata Management: A User-Centered Manifesto Carol A. Hert PNCASIST May 15, 2004.
Advertisements

Achieve Benefit from IT Projects. Aim This presentation is prepared to support and give a general overview of the ‘How to Achieve Benefits from IT Projects’
1 Presented By: Sonya Hawkins.  Discuss Scope  Discuss Requirements 2.
Vision Session Content and Users Group. Straw Man Proposal – Vision: Comments Include statement of whose library it is – ownership, stakeholders –Is ownership.
Software Architecture in Practice (3 rd Ed) Introduction The Many Contexts of Software Architecture Architecture in a Technical Context Architectures inhibit.
APS Teacher Evaluation Module 9 Part B: Summative Ratings.
Systems Analysis and Design 9th Edition
Chapter 2.
1 Fundamental Principles of Solution Design and Implementation Chapter 3.
Esri International User Conference | San Diego, CA Technical Workshops | What you Need to Know About Managing an Enterprise GIS Project Gerry Clancy Glenn.
Fatima Al-Abdulla Managing Analysis. Outline:  Introduction  Why managing Analysis? 1-Documenting Analysis 2-Assigning Responsibilities 3-Communicating.
7M822 UML Introduction 7 September 2010.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Chapter 3 The Knowledge Leader
Software Engineer Report What should contains the report?!
ASEC/SLDI FINANCIAL MANAGEMENT COURSE 1 TOPIC: STRATEGIC PLANNING, OPERATIONAL PLANNING AND BUSINESS PLANNING MODULE 5 BY: CORAT AFRICA.
The Multi-Site RAM Experience Norm Rabin Senior Quality Manager, Calibration Roche Diagnostics, Indianapolis.
Six Sigma Black Belt Project Information Prepared: July 20, 2004.
Action Research In Organizational Development. Action Research Coined by Kurt Lewin (MIT) in 1944 Reflective process of progressive problem solving Also.
Project Management What The Heck Is That?. Why Do We Need Project Management? Critical towards delivery of effective IT initiatives Ensures we align projects.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
2008 Adobe Systems Incorporated. All Rights Reserved. Developing an eLearning Strategy at a Nigerian University By Jerome Terpase Dooga, Christopher Tony.
RUP Fundamentals - Instructor Notes
Transaction Processing Systems and System Development Life Cycle
ZEIT2301 Design of Information Systems
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Project Management for RIM Professionals Last Updated: 3/13/2011 Sarina Arcari, PMP VP Implementation & Product Planning Amerigroup Corporation 3/15/11.
1 ©Copyright Dr G Sieff | IC Growth Group | | ph Strategy Mastery Programmes October 2012.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
E P R E nterprise P erformance R eporting A Fundamentally Better Way to do Business TM.
Bring Your Business into the 21 st Century : Part 1 WasteExpo 2011 Improving Your Financial Management System.
The Challenge of IT-Business Alignment
IIBA - Cedar Rapids Chapter Thursday, Sept. 22, 2011.
Kelly J. Harris SEARCH Deputy Executive Director
Creating a Shared Vision Model. What is a Shared Vision Model? A “Shared Vision” model is a collective view of a water resources system developed by managers.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Requirements (Advanced Topics) “Walking on water and developing software from a specification are easy if both are frozen.” --Edward V Berard.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5 Leffingwell.
Christian Chace Patent Process Reengineering Team September 8, 2010 Patent Process Reengineering Team as part of the Patent End-To-End Processing Team.
Component 4: Introduction to Information and Computer Science Unit 9/Part a: Components and Development of Large Scale Systems.
Project Management Cross lifecycle Activity
ETwinning contact seminar 2nd – 4th June, 2011 Project management Maja Mušnjak:
Topic 18 Leadership and Change / Leadership in the Future (NOTE: Material in this topic will be on Exam 2 only if you choose it as your essay option.)
SACS/CASI District Accreditation  January 2007  April 2007  May 2007  January – April 2008  Board Approval for Pursuit of District Accreditation.
Requirements Management Overview NIGMS Software Development.
Knowledge Translation Curriculum Module 1: An Introduction to KT Lesson 4 - KT Approaches and Tools.
Chapter 3 The Knowledge Leader
CI R1 LCO Review Panel Preliminary Report. General Comments –Provide clear definition of the goals of the phase (e.g. inception), the scope, etc. in order.
ITEC 370 Lecture 6 Requirements. Review Requirements –What are some of the stages of the requirements gathering process? –What is the end result of this.
1 Systems Analysis & Design 7 th Edition Chapter 2.
The B uff. The Buffs Outline 1. Summary of last presentation 2. Current iteration and Progress 3. Plan for next iteration.
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Systems Analysis & Design 7 th Edition Chapter 2.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
Requirement Elicitation Nisa’ul Hafidhoh Teknik Informatika
Windows 7 Ultimate
Chapter 5 – System Modeling
Requirements Inception
Chapter 5 – System Modeling
Requirements Engineering
Requirements Inception
Event Scheduling System
Requirements Inception
What you Need to Know about Managing an Enterprise GIS Project
Chapter 4 System Modeling.
Template for methodological application
Presentation transcript:

Product Vision & Project Scope By: Bryan Peterson

Summary of Topics Vision and Scope Document – What is it? – Why do you need it? – What does it contain?

Humor

Intro The vision and scope document collects the business requirements into a single document that sets the stage for the subsequent development work.

Need for vision and scope doc The user requirements and software functional requirements must align with the context and objectives that the business requirements establish. A project that lacks clearly defined and well- communicated direction invites disaster. A clear vision and scope is especially critical for multi-site development projects, where geographical separation inhibits the day-to-day interactions that facilitate teamwork.

Defining Terms Product vision: aligns all stakeholders in a common direction Project scope: identifies what portion of the ultimate long-term product vision the current project will address. The vision applies to the product as a whole and will change relatively slowly. Scope is more dynamic than vision.

Project Vision Diagram

Vision and Scope Document

Conclusion The product vision and project scope is important in giving a project direction. It manages scope creep and “gold-plating” Having a clearly defined product vision and project scope can save you time as a requirements analyst in defining use cases and their implementation priorities.

References Wiegers, Karl E. Software Requirements. 2 nd edition. Microsoft Press, 2003.