Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders.

Slides:



Advertisements
Similar presentations
Presentation suggestions:
Advertisements

Christophe Fiessinger Senior Technical Product Manager Microsoft Corporation.
Lecture 5: Requirements Engineering
Renato Pinto López TUM18 - UPM. Sprint Planning Meeting ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY.
Essence Workshop June 20, Applying Essence in Practice Ed Seidewitz Ivar Jacobson International.
Making Sense of Projects The Ability to Lead and Other Basics.
Shared Vision It all starts with a “Vision Statement”
Create New feature Approved Change request Create User Stories for the feature Add User stories to Target Process backlog User Stories – 1.Create Story.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 6 Initiating and Planning Systems Development Projects 6.1.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Introduction to software project management. What is a project? One definition ‘a specific design or plan’ ‘a specific design or plan’ Key elements non-routine.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
1 Software project management (intro) An introduction.
Modern Systems Analysis and Design Third Edition
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.
socio-organizational issues and stakeholder requirements
FatMax Licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 LicenseCreative Commons Attribution-NonCommercial-ShareAlike 2.5.
INCOSE 1 st reactions. One other area that struck me has the sheer number of levels of proficiency—in ours we are going with 5 and the first one is limited.
6 steps to a really good TOK essay Modified from Eileen Dombrowski.
Initiating and Planning Systems Development projects
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
RUP Requirements RUP Artifacts and Deliverables
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
2/18/14 copyright Quazarconsulting.com.  Understand the role of the Product Owner  Understand the role of the Product Manager  Compare and contrast.
Chapter 2 Introduction to Requirements Management
Welcome to the APAN SharePoint User Group Jan 15, 2015.
© The McGraw-Hill Companies, An Introduction Chapter 1 Software Project Management 4 th Edition Robert Hughes and Mike Cotterell.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Agile Modeling Theory. 2 Agile Modeling (AM) AM is a chaordic, practices-based process for modeling and documentation AM is a collection of practices.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Feasibility Study.
Presenter: 陳秋玉 1.  Extreme programming Extreme programming  On-site customer On-site customer  Benefit Benefit  Characteristics of a good customer.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
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.
Agile Methods Chapter 30. Agile Methods Key points ▫No method fits all projects or organizations ▫In General  A process to elicit, organize, document,
Software Requirements (Advanced Topics) “Walking on water and developing software from a specification are easy if both are frozen.” --Edward V Berard.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
What is a Process? A logically related set of tasks performed to achieve a defined business outcome. A structured, measured set of activities designed.
Unit III Goals & Objectives. Goal & Objectives The ENDS versus the MEANS Goals are measurable statements, describing what can outcomes can be reasonably.
Tools: Project Charter (Tab 4)
5/30/20161 Iterative Project Management Chapter 2 – How Do Iterative Projects Function? Part 1 Iterative Project Management / 01 - Iterative and Incremental.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Team Skill 3 – Organizing Requirements & Product Management (Chapters of the requirements text ) Sriram Mohan/Steve Chenoweth RHIT 1.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Software Requirements and Design Khalid Ishaq
CS 5150 Software Engineering Lecture 7 Requirements 1.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Why Practical Design…Why NOW… 1 Practical Design in ODOT (Tab 2) ? Training ? 2010 Cathy Nelson, PE Technical Services Manager/ Chief Engineer.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Team Skill 3: Defining the System The Vision Document (16) 1.
Technical Writing Unit This Week ► Presentation guidelines ► Ideas for displaying data.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
 System Requirement Specification and System Planning.
Project 1: System Concept
[Authors] [Affiliation]
Sterling Examiner Preparation
Use Case Modeling Part of the unified modeling language (U M L)
How to deal with requirements in an Agile context?
Presentation transcript:

Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders ? Can you demonstrate that all stakeholders agree upon the described vision?

 Having a clear vision is key to developing a product that meets your stakeholders' real needs.  It captures very high-level requirements and design constraints, giving the reader an understanding of the system to be developed

 Problem Definition ◦ Why is it really that we wants to start development of this system? The problems behind the problem.  Organizational issues?, Law issues ?, Technical issues? Customer issues?.....  Needs ◦ What does the organization/the customer need in order to meet the issues mentioned above? (not described as technical solutions)  Features ◦ Which features can an IT system provide so that the customer needs are fulfilled?  Stakeholders ◦ Who are the team? Who are the stakeholders? Who are the users?..  Competences and qualifications ◦ Which competences and qualifications are needed in the team in order to meet this vision?

 Here you find relevant information and inspiration on UP pracitces etc. e.g. the vision document   Look under work products/requirements for description of Vision development  Remember the most important is NOT the document BUT the communication

 Introduction to Agile Practices: XP Game Link to a site with information to download

1. Start with 2 stories 2. Which one takes most time? 3. Take next card -> sort it 4. Continue with all stories 5. Simplest story gets 2 effort points