Project Resource Planning Key Software Project Resources: 1.“Human” Resource 2.“Methodologies and Processes” Resources 3.“Tools and Equipment” Resources.

Slides:



Advertisements
Similar presentations
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
Advertisements

Approaches to Systems Development
Tietojärjestelmien peruskurssi Software engineering Malin Brännback.
Software Configuration Management
Managing the Information Technology Resource Jerry N. Luftman
Unit Five – Transforming Organizations
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Computers: Tools for an Information Age
Applied Software Project Management 1 Introduction Dr. Mengxia Zhu Computer Science Department Southern Illinois University Carbondale.
1 Chapter 6 Systems Development. 2 Learning Objectives  Know the characteristics of systems development.  Understand what professional systems analysts.
Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Web Development & Design Foundations with XHTML
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Project Management and Scheduling
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
Introduction to Computer Technology
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”
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.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Software Development Concepts ITEC Software Development Software Development refers to all that is involved between the conception of the desired.
Web Developer & Design Foundations with XHTML
Systems Analysis and Design: The Big Picture
S/W Project Management
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Applied Software Project Management Andrew Stellman & Jennifer Greenehttp:// Applied Software Project Management Chapter 1: Introduction.
Software Project Management Introduction to Project Management.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Best Practices By Gabriel Rodriguez
Software Testing Life Cycle
Web Development & Design Foundations with XHTML Chapter 10 Key Concepts.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Configuration Management (CM)
Software Engineering Management Lecture 1 The Software Process.
Basic of Project and Project Management Presentation.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
An Introduction to Software Engineering. Communication Systems.
1 Introduction to Software Engineering Lecture 1.
SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
 Project management is the organization and management of resources (i.e. people, information, tools and machines, materials, time, capital and energy)
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
System Requirements Specification
State of Georgia Release Management Training
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section A 1.
Basic Concepts and Definitions
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Project Management Enabling Quality Marien de Wilde, PMP April 2007.
Test Planning The purpose of test planning  The areas to consider in planning.
11 ADM2372 Management Information Systems (MIS) Chapter 10 – Part I Systems Development Chapter 10 – Part I Systems Development.
CS 501: Software Engineering Fall 1999 Lecture 22 (a) Managing the Software Process (b) Software Reuse.
Systems Development Process Developing our own software The Business Perspective Copyright © 2016 Curt Hill.
Chapter 12: Planning for Electronic Commerce
Software Configuration Management
Fundamentals of Information Systems, Sixth Edition
User Stories Applied, Mike Cohn Chapter 1: An Overview
Methodologies For Systems Analysis.
Web Site Project Management
Chapter 1 (pages 4-9); Overview of SDLC
Presentation transcript:

Project Resource Planning Key Software Project Resources: 1.“Human” Resource 2.“Methodologies and Processes” Resources 3.“Tools and Equipment” Resources

1. Human Resource How Many People? What Attributes or What Type of people? –Technical Skills –Experience Level –Non-technical Skills –Personal Character Attributes When scheduled to be on-board? Go back to the initial schedule derived from WSB

Schedule “Evolved from WBS” Tasks Resp.MayJuneJuly Req Design Code Test Choose Specific # of Resources

Consider the People Responsibility Column in Schedule How Many? –Start with the initial estimate and assumption for each major task listed. What Attributes? –Based on task type, specify the: required technical skill required experience required non-technical skills required temperament and personal traits When ? –Utilize the initial schedule layout and estimate the timing

from schedule - - -Expressing the “People Needs” Skilled Personnel MayJuneJuly Req Analyst Designer Programmer Tester Assuming that you agree with testing schedule

“Sample” Skill Descriptions If the Organization already has skills and level descriptions, then use them Brief Examples –Requirements Analyst : ‘j’ application domain knowledge by education or ‘x’ years of experience in the domain ‘j’; technical skill knowledge by education or ‘y’ years of experience; ‘z’ years of prior experience in performing the requirements analysis task; good written and verbal communications skills; disciplined work habits; can travel 75% of time, etc. Depending on the ‘x’, ‘y’, ‘z’ and other information the requirements analyst may be classified as a senior, normal, or junior level; one may use the levels once they are defined and agreed upon. –Programmer : ‘B-language’ development environment skills by education or by ‘x’ years of experience; ‘j’ application domain knowledge by education or by ‘y’ years of programming in ‘j’ application domain area; good written communications skill; high energy; can work excessive overtime, etc.

If You Know the Individual Resources, Start with them Skilled Personnel MayJuneJuly Req Analyst: - B. Sam Designers: - T. Book - M. Soso Programmers: - new hire Tester: - B. Sam recruiting time What do we do with this time? Don’t need this much time.

Perhaps We Can Re-consider ? Skilled Personnel MayJuneJuly Req Analyst: - B. Sam Designers: - T. Book - M. Sosa Programmers: - new hire Tester: - M.Sosa recruiting time Pick the next best qualified candidate ?

Making Trade-off (No Candidate is “Perfect”) 1.What is/are the most important attribute(s) required to perform the task? –Does the candidate meet it/them? 2.What is/are somewhat important attribute(s) needed to perform the task? –How many of them does the candidate meet? What are some example (criteria) of trade-off? –Financial cost versus qualifications (think about the project goals) –Person’s desire /career aspirations versus project goals (think about the goals of project and the person) –**Can anything else be modified --- such as task sequence or dates ? **

Project Manager’s “In-sourcing” or “Out- sourcing” Decision Making Considerations Large projects with enormous amount of effort and time required in HR recruiting and all the follow-on activities The amount of lead time available for recruiting (short project schedule) Amount of control over the resources Amount of Cost Savings Information Security and Proprietary Information Ownership Skills Available Infrastructure (process, tools, timing) has been over-emphasized & over-valued sometimes comes back to the bite us

2. Process and Methodologies Process describes a set of activities or tasks to accomplish something. –List the activities –Sequence the activities (including parallel activities) –entrance and exit criteria of the activities Methodology describes the principles and rules to perform and accomplish an activity –description of the principle : the intended “goals” of the methodology and why the procedure will achieve the goals –description of the rules : the actual sub-steps that make up the procedure (Most do not have this)

Process and Tasks What is the overall process? –What tasks should be included? And why? –Have we already considered this before and may have an existing process that may be applied –Decision making is based on goal type of project current state For each of the task –What is/should be the methodology? And why? –Decision making is based on goal type of project current state

Process: Major Tasks for Software Projects They all seem to have: –Requirements Processing –Design –Implementation –Testing –Packaging and Releasing Does this mean every project uses the same process ? –We need to look deeper –****When do we have to have this decision? ***** Before we embark on the project; before we embark on the task! Where is the attractiveness of Waterfall? and of Agile? ---- of Spiral?

Methodology to Accomplish Major Task Example: i) Requirements Gathering, ii) Analysis/Validation, and iii) Representation is something we have talked about in class and in an earlier chapter: –how much of the steps do we need to complete for the software project at hand --- based on goal what we may suspect as possible problem areas * Some of the students in the capstone course are “experiencing” the challenge of competitive analysis as part of requirements processing --- and they have never worried abut this type of activity

Methodology to Accomplish Major Task Another Example: What about Implementation Task?: –Should we have programming standards? Who should develop one if we need one? –documentation convention –naming convention –technique convention : (size, control structure, data exchange, UI screens, etc.) How should it be monitored? –Should there be a prescribed coding language? –Is unit testing part of implementation? Should unit testing follow a guideline/template? Who should develop one if needed? –Should there be code inspection ? –Answer these by asking what are my goals ? Quality Maintenance needs Etc. Do I need to worry if the project size is small ?!

3. Tools and Equipment General: –Hardware personal (desktop/laptop)computers printers servers –Communications Connections intranet internet –Software operating system database office package communications package

Software Project Related Tools Tools for specific tasks –requirements documentation and analysis –design documentation and analysis –prototyping and modeling –editors, compilers, debuggers and development kit –test script development and execution –performance testing and analysis –key stroke capture –execution monitor and coverage –packaging diskettes and CD –builds Cross-Project tools –configuration management –statistical analysis –back-up / recovery –project control and management

Note that in “Your (this class’s)” case (How would Resource Management Work?) You have an end date that’s already fixed. –You must lay out the schedule based on that fixed length You also know how many people (and their skills) are on your staff (another fixed parameter) So you only have a few things to play with namely : Functionality Process Technology/Methodology People assignment (can’t really outsource either! ) Goals Tools