Team Skill 1 - Analyzing the Problem Steve Chenoweth & Sriram Mohan Pages 43 – 52 in Requirements Text.

Slides:



Advertisements
Similar presentations
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.
Advertisements

Hogeschool van Amsterdam Interactieve Media The art of pitching Hoorcollege marketing blok 2 week 6.
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini September 28, 2011 PDCA Training Series 2 PLAN, Part 2.
Workbook 1: Crafting Your Value Proposition Workbook Template
Inception: Starting a New Project Needs Features Vision.
Writing winning proposals. Why write proposals? Work in industry and business is done through proposals The process: ▫Requests for Proposals (RFPs) identify.
1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text.
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.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
Supercharging DMAIC IT’S TIME TO USE THE POWER OF THE COLLECTIVE MIND.
Analyzing a problem by identifying causes and effects.
7M822 Software Requirements Introduction 7 September 2010.
Waniwatining Astuti, M.T.I
Problem Analysis The goal of problem analysis is to gain a better understanding of the problem being solved before development begins Gain agreement on.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
RUP Requirements RUP Artifacts and Deliverables
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Data Flow Methodology Steve Chenoweth & Sriram Mohan Question 6.
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
Writing a Problem Solution Essay. Analyzing the Problem Explore What You Know About the Problem. Figure out what you know now about the problem and what.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Class #2-4: Entry, Contracting and Proposal Writing.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Software Requirements and Design Khalid Ishaq
Chapter Fourteen Communicating the Research Results and Managing Marketing Research Chapter Fourteen.
Chapter 31 Your Prescription for Requirements Management.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
Team Skill 1 Analyzing the Problem
FishboneFishbone Six Sigma Foundations Continuous Improvement Training Six Sigma Foundations Continuous Improvement Training Six Sigma Simplicity.
1 Class #1 Assignments Mark E. Sampson UPDATED 8/02/04 EMIS 8390 Systems Engineering Tool—applying tools to engineering systems.
Problem Analysis 1. What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those.
Rational Requirements Management with Use Cases v 5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
Project Charter START IT! By Catherine B. Calio, PMP
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Consulting Guidelines.  This is not your business!  You can only make recommendations based on the consulting agreements objectives  You may recommend.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
SYS366 Problems and Problem Statement. What is a problem? Gause and Weinberg (1989): A problem can be defined as the difference between things as perceived.
Ensuring Project Requirements Meet Customer Needs Project Planning.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
Objectives of the session
Cause effect identification using Fishbone Diagram Powered by: Jazz PresentationJazz Presentation.
Unit 8 – Project Management Lesson 4 –definition of scope.
5 Why analysis By its very nature, a Lean Six Sigma program requires a number of changes throughout the organization. That’s what we are trying to do right?
Crafting Your Offer & Market Value Proposition By Ed Downes.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
1 Team Skill 1 Analyzing the Problem … Part 1: 5 steps in Problem Analysis Based on “Software Requirements Management, A use case approach”, by Leffingwell.
Is 581 assist Inspiring Minds/is581assistdotcom FOR MORE CLASSES VISIT
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Team Skill 1 - Analyzing the Problem
Recall The Team Skills Analyzing the Problem (with 5 steps)
INF 342 Enthusiastic Study/snaptutorial.com
GHSP Problem Solving Team Champion: Team Members: Team Mentor:
DMAIC Roadmap DMAIC methodology is central to Six Sigma process improvement projects. Each phase provides a problem solving process where-by specific tools.
Killer Project Management Best Practices
Overview What Are Cause & Effect Diagrams?
Project Charter.
2019 INNOVATION ACCELERATOR Presentation Slide Template
Presentation transcript:

Team Skill 1 - Analyzing the Problem Steve Chenoweth & Sriram Mohan Pages 43 – 52 in Requirements Text

Requirements Team Skills 1.Analyzing the Problem 2.Understanding User and Stakeholder Needs 3.Defining the System 4.Managing Scope 5.Refining the System Definition 6.Building the Right System

Problem Analysis “ the process of understanding real world problems, user needs and proposing solutions to meet those needs” “ problem is defined as the difference between things perceived and things desired” Not every problem needs a new solution

The Five Steps in Problem Analysis 1.Gain agreement on the problem 2.Understand the root causes 3.Identify the stakeholders 4.Define the solution system boundary 5.Identify the constraints imposed on the solution

Step 1: Identify Stakeholders “ anyone who can be marginally affected by the implementation of a new system or application”  Who are the users?  Who is the customer?  Who else will be affected?  Who will approve the system?  Who will maintain the system? Who else cares?

In-Class Project  This project example will be used just in class – in today’s class and in following ones. Don’t take it outside the class at all.  Degree Planner  What does the client think this is?  He’s sent you a few notes – see below this slide!  You’ll have a chance to ask him questions, in class, too.

Team Work - Stakeholders  As a team try to add to the stakeholders for the “Degree Planner” project. First, exchange information with the others on your team. You may discover stakeholders that you missed, which other people thought of. Then, I will act as the client as far as the sample project is concerned, you can question me for 10 minutes. Some of the time, people may be asking about stakeholders. Write down any additional stakeholders you hear about.

The Five Steps in Problem Analysis 1.Gain agreement on the problem 2.Understand the root causes 3.Identify the stakeholders 4.Define the solution system boundary 5.Identify the constraints imposed on the solution

Step 2: Agree on the Problem  Write the rest of the problem statement, using the format on the quiz. A problem statement is the problem to be solved, written in a standardized format It helps to know the benefits the proposed system will offer from a customers perspective. There may be more than one statement.

Our Format for Problem Statements  The problem of: A description of the problem solved by the system  Affects: The people affected by this new system  And results in: The impact of the problem on stake-holders  Solution Benefits: Indicate the solution and list a few benefits

Elevator Statement  According to Wikipedia In business jargon an elevator statement (or elevator pitch) is a short concise and compelling statement about a business or a business situation that can be delivered in the time it takes for an imaginary elevator ride.

The Five Steps in Problem Analysis 1.Gain agreement on the problem 2.Understand the root causes 3.Identify the stakeholders 4.Define the solution system boundary 5.Identify the constraints imposed on the solution

Step 3: Find Root Causes  How do you find problems and their causes? Don’t assume “ ask and ask again ”

Fishbone or Ishikawa (Kaoru Ishikawa) diagrams Problem in head of fish Draw major bones for different sources of the problem Expand recursively.

An Example Fishbone Diagram Lousy Meals Same old every day Lousy cooks Too far from suppliers Lousy kitchen Poor education Poor attitude Have to get up early Underpaid

Tool for Drawing Fish Bone Diagrams  Template on course website [under Resources]  Visio has a nice template  Powerpoint can be used  has the original of the template

Final Step  Draw a fish bone diagram for the “Degree Planner” project and turn it in at the end of class, on your quiz.