SENG 613 - Software Life Cycles1 Exercise 3 – JAD Session Using the Management Guide form the last exercise simulate a JAD session Following the agenda.

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Advertisements

Developing a Balanced Score Card Session 1 Viki Massey, Quality Coordinator A Joint Venture of London Health Sciences Centre and St. Josephs Health Care.
Money Management. Vocab Words Budget: a spending plan to help you manage your money Needs: items that you are unable to live without Wants: items you.
Program Management Office Department of Innovation & Technology City of Boston Kickoff Meeting.
TC 4, 6, 10, 13 On-line Trading System 1, 2, 4
Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 16, Methodologies: Scrum.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
IT Strategic Planning Project – Hamilton Campus FY2005.
PPA 691 – Policy Analysis Brainstorming and Assumptional Analysis Procedures.
Feb. 6, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #7 Tuesday, Feb. 6, 2001.
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.
IS Consulting Process (IS 6005) Masters in Business Information Systems 12 th Mar 2010 Fergal Carton Business Information Systems.
Facilitation Richard Fisher. 10/9/2000Facilitation - Richard Fisher2 Facilitated Sessions A structured meeting technique designed to gather information.
HIT241 - COST MANAGEMENT Introduction
The chapter will address the following questions:
The chapter will address the following questions:
2014 Work Planning Local Program Leadership Team.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
POWERED BY: A Successful Adoption Of Technology #NPPROTGC Ron Marzitelli Assistant Vice President of Information Technology School of Business & Technology,
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 16, Meeting Management with Scrum.
Problem Identification
Strategies for organizing and conducting effective meetings Informational meetings Collaborative decision making meetings Committee on Special Education.
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
Estimation Chapter 3 Applied Software Project Management, Stellman & Greene.
1-2 Training of Process FacilitatorsTraining of Coordinators 6-1.
1 IMPAC II SW Development Life Cycle Requirements Analysis Preliminary Design Detailed Design PrototypeBuild - Test Documentation Conversion & Pilot Production.
Team Skill 2 Understanding User and Stakeholder Needs Requirements Workshop (11)
Chapter 4: Project Cost Management
ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
CIS 499 Senior Seminar Introduction to IT project management.
Dictionary Lesson Finding and Defining Words. Brainstorm a location Think of a place or location –Example – the classroom.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
Copyright Irwin/McGraw-Hill Joint Application Development Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten.
Requirements Gathering How do we find out what we are supposed to be building?
IS2210: Systems Analysis and Systems Design and Change Twitter:
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Service Component Registry and Repository (SCRR) April 26, 2007 Lico Galindo 2007 Exchange Network National Meeting.
LEADING DECISION GROUPS APAMSA Leadership Development Module.
1 Facilitation Facilitation is the process of making something easier or less difficult…
Oktalia Juwita, S.Kom., M.MT. SYSTEMS DEVELOPMENT Dasar-dasar Sistem Informasi – IKU1102.
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.
Requisite Skills for IS Management and Interpersonal Skills.
SENG Software Life Cycles1 Exercise 2 – Management Guide As a group fill in the Management Guide template provided First decide on your roles as.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Effective Meeting Skills
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
Quality Improvement Breakout Neil Korsen, MD, MSc MaineHealth April 16-17, 2009.
Assessment Data Professional Collaboration Russ Romans and Mike Loughrey RDA.
Requirements Gathering
How to Organise and Carry Out Meetings Top tips. N 3.3.
Leadership Skills. Team Meetings Set the agenda by defining goals and desired outcomes Set the agenda by defining goals and desired outcomes Keep the.
Unit (6) Delivery Of Instructional Strategies. What Is The Teaching and learning Environment?
SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.
ITIL Project Change Management Workshop 7 February 2007
Strategies for organizing and conducting effective meetings Informational meetings Collaborative decision making meetings Committee on Special Education.
Fundamentals of Software Development 1Slide 1 Team management What can you do to help your team work effectively?What can you do to help your team work.
Team management What can you do to help your team work effectively?
Chapter 12, Rationale Based Meeting Management
Desired Discussion/Outcome
Summarizing Our Models to Date
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Participative Process Reviews
Every meeting has three parts: Ramp-Up, Meeting, Follow-Up.
Chapter 12, Rationale Based Meeting Management
Employee engagement Delivery guide
Scrum in Action.
Joint Application Development (JAD)
Project Name Here Kick-off Date
Presentation transcript:

SENG Software Life Cycles1 Exercise 3 – JAD Session Using the Management Guide form the last exercise simulate a JAD session Following the agenda spend the allotted time on the various areas Scribes should record concise point-form notes about the discussion Facilitators will try to guide the discussion and ensure everyone has an opportunity to speak

SENG Software Life Cycles2 Exercise 3 – JAD Session The goal of this exercise is to produce a prioritized list of features/requirements for your proposed system Keep the number of requirements below 10, remember the amount of time we have Take on the roles you previously defined for yourselves and start a meeting using the supplied agenda Users speak up about things that you want the system to do! Remember the scope of the project

SENG Software Life Cycles3 Exercise 3 - JAD Session Agenda Discuss and resolve open issues from the management definition guide and list any required action items (10 min.) Brainstorm List of Features & Services – What Additional Ones do Your Stakeholders Need? Desire? (15 min.) Prioritize your list of features