Task Analysis is Part of Planning Once we have completed planning on the deliverables and contents of the deliverables, we need to plan out “how to accomplish”

Slides:



Advertisements
Similar presentations
WBS-Construction of House (Example) WBS Dictionary
Advertisements

Work Breakdown Structures
CS487 Software Engineering Omar Aldawud
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
Software Design Process A Process is a set of related and (sequenced) tasks that transforms a set of input to a set of output. Inputs Outputs Design Process.
Project Resource Planning Key Software Project Resources: 1.“Human” Resource 2.“Methodologies and Processes” Resources 3.“Tools and Equipment” Resources.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Project Management.
Degree and Graduation Seminar Scope Management
Project Management Overview. Project driven or Non Project driven Organizational “drivers” Marketing Engineering Manufacturing.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Project Planning Dr. Jane Dong Electrical and Computer Engineering.
Your Presentation Title Names of Team members Advisor name EE496A Midterm Presentation Fall, 2006.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Software project management (intro)
Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.
PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT
Project Management and Scheduling
Task Analysis is Part of Planning Once we have completed our plan on what to deliver and the contents of deliverables (via requirements), we need to: plan.
Project Management Fundamentals Project Organization and Integration
1 L07SoftwareDevelopmentMethod.pptCMSC 104, Version 8/06 Software Development Method Topics l Software Development Life Cycle Reading l Section 1.4 – 1.5.
DCT 1123 PROBLEM SOLVING & ALGORITHMS INTRODUCTION TO PROGRAMMING.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1Spring Quarter Project Management Week 2 Day 2.
How to integrate the parts of your project to achieve success.
S/W Project Management
Client Logo LEAN ENTERPRISE Implementation Workshop.
After Lesson 6 next is Lesson 13 to fit topic on Software Development SOFTWARE PROJECT MANAGEMENT.
Open Workbench By Wilmer Arellano Spring Statement Of Work (SOW) A statement of work (SOW) is a document used in the Project Development Life Cycle.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
Successful IT Projects slides © 2007 Darren Dalcher & Lindsey Brodie Successful IT Projects By Darren Dalcher & Lindsey Brodie
Planning the project Project Management (lecture).
Software Project Planning Chapter 2 Applied Software Project Management, Stellman & Greene.
Project Management Practices Vesa Tenhunen University of Eastern Finland LUMA Centre
Chapter 13 Software Project Management. Project Management “Process” Why do we need project management? Why can’t we just follow one of the software development.
Week 2 Seminar: Project Scope Management
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
CMSC 1041 Algorithms II Software Development Life-Cycle.
Work Breakdown Structure Use and Demo
Chapter 7 Software Engineering Introduction to CS 1 st Semester, 2015 Sanghyun Park.
Applied Software Project Management
S/W Project Management Software Project Planning (POMA) Task Analysis.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
Project Schedule PLAN IT!. Project Schedule Project Schedule is based on Work Breakdown Structure (WBS) Define the WBS correctly or the Project Schedule.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
Effort.vs. Software Product “Quality” Effort Product “Quality” Which curve? - linear? - logarithmic? - exponential?
College of Information Systems & Technology © 2001 University of Phoenix. University of Phoenix is a registered trademark of Apollo Group, Inc. in the.
Requirements Document Work Breakdown Structure. Schedule DateTooicAssignment 1-Oct-08work breakdown/features breakdown 8-Oct-08agile methodsrequirements.
Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
T Project Review Muuntaja I1 Iteration
1 11/2004 – N.Campanis for MPUG Western NY Chapter Working Session Nick Campanis Presented to MPUG – Western NY Chapter Working Session November 10, 2004.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
1 Week 11 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
WEEK 3 Project Planning.
Software project management 3rd Umer khalid Lecturer University of Lahore Sargodha campus.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.
Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 3 Executing & Controlling & Closing Projects.
© 2008 Prentice Hall6-1 Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and.
Algorithms II Software Development Life-Cycle.
Project management assignment, Spring 2017
WORK BREAKDOWN STRUCTURE
Team member, Team member and Team member
Work Breakdown Structure
Software metrics.
Team member, Team member and Team member
Presentation transcript:

Task Analysis is Part of Planning Once we have completed planning on the deliverables and contents of the deliverables, we need to plan out “how to accomplish” the deliverables

Task Analysis Task analysis is domain dependent: –build a desk –plant a tree –write computer program –build a road –make a spaghetti dish Software project task analysis is no different –you need domain knowledge to do this well computer science software engineering information technology possibly application domain Task Analysis: Defining and Sequencing the sub-activities of a Task

From Requirements to Work Breakdown Structure (WBS) We get 2 sets of information from Requirements: –required deliverables to the customers –descriptions about those deliverables The first “high level” task of sequencing the required customer deliverables may seem simple, but --- consider the example listed for a project: –code –user guide –support plan –development process document Note: date is purposely not included, yet WBS: - is the listing and sequencing of the work activities needed to produce the required deliverables. (Note that there may be concurrent activities.) - a way to do Task Analysis

External Deliverables of A Project Support plan code develop. Process doc user guide consider these

A Sequence of External Deliverables Support plan code develop. Process doc user guide End 1.- Do you all agree ? Discuss - what do you need to decide here. 2.- Also decide if the sequence of deliverables “equal” sequence of activities (tasks) to produce the material

Representing in “Schedule” form Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGz Gy Gx Gw New parameter All the same length and no overlap Deliverables became Tasks !

Effort Analysis Estimation of “Effort” for each deliverable –need to understand the subtasks required to produce the deliverable and any intermediate deliverables that may be required –need to break it (deliverable/task) down more by sub-components to the level where : –one person can do the task –skill of the person can be described –actual task can be described and size estimate has some comparable “past history” or “algorithm” –a common measurement: effort = size/productivity How important are these?

A Deeper Work Breakdown Structure (WBS) for “Developing” A Support Plan Interview Customer for input Analysis and Develop Outline Review with Customer Develop the whole Plan Final Review End 1 cycle only O.K. Not O.K.

Effort Analysis & A Deeper Work Breakdown Structure (WBS) of “Developing” A Support Plan Interview Customer for input Analysis and Develop Outline Review with Customer Develop the whole Plan Final Review End O.K. 1/2 p-day 3 p-days 1/2 p-day 5 p-days 1/2 p- day ** - Do not forget about wait time - how many people are required ? - what kind of skill & background ? p-day estimate based on the assumptions: 1. size of (how much) work is estimated. 2. Productivity of the assigned person * note

Assuming WBS is Performed for Each Major Deliverable Support plan code develop. Process doc user guide End Assume you agree with the sequence For each of the major deliverables, estimate the required effort in p-days via WBS (*** these are person-days ---- want to get to individuals) 7 p-days 10 p-days 25 p-days

Improving on Task “Schedule” Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGw Gy Gx Gw Overlapping, different length Having chosen specific resources

Milestones in “Schedule” Tasks Resp.MayJuneJuly Proc Code User Guide S.PlanGw Gy Gx Gw Major Minor

General flow of WBS to Timeline Schedule Identify the deliverables For each deliverable: identify the tasks for completing the deliverable Sequence the tasks For each task: -Estimate the needed size of work for effort analysis For each task: -Estimate the productivity of the assigned resource for effort analysis For each task: compute the “effort” timeline for that task by dividing size of work by productivity After all the effort for all the tasks for all the deliverables are computed do following step Lay out the effort timeline for all the ordered tasks needed for each of the deliverables