Project Resource Planning - PowerPoint PPT Presentation

1 / 18
About This Presentation
Title:

Project Resource Planning

Description:

Designer. Programmer. Tester. 1. 2. 2. 1. Assuming that you agree with ... Designers: - T. Book - M. Soso. Programmers: - new hire - new hire. Tester: - B. Sam ... – PowerPoint PPT presentation

Number of Views:216
Avg rating:3.0/5.0
Slides: 19
Provided by: fts2
Category:

less

Transcript and Presenter's Notes

Title: Project Resource Planning


1
Project Resource Planning
  • Human Resource
  • Methodologies and Processes
  • Tools and Equipment

2
Human Resource
  • How Many
  • What Characteristics
  • What Technical Skills
  • How Much Experience
  • Non-technical Skills
  • Strong Character Attributes
  • When
  • Go back to the initial schedule derived from WSB

3
Schedule Evolved from WBS
Choose Specific of Resources
Resp.
May
June
July
Tasks
Req
1
Design
2
Code
2
Test
1
4
Consider the People Responsibility Column
  • How Many?
  • Start with the initial estimate and assumption
    for each major task listed.
  • What characteristics?
  • 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

5
Expressing the People Needs
Skilled Personnel
May
June
July
Req Analyst
1
2
Designer
Programmer
2
1
Tester
Assuming that you agree with testing schedule
6
Sample Skill Descriptions
  • If the Organization already has skills and level
    descriptions, then use them
  • Brief Examples
  • Requirements Analyst j 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.

7
If You Know the Individual Resources,Start with
them ------
Skilled Personnel
May
June
July
Req Analyst - B. Sam
Designers - T. Book - M. Soso
recruiting time
Programmers - new hire - new hire
What do we do with this time?
Tester - B. Sam
8
Perhaps We Can Re-consider ?
Skilled Personnel
May
June
July
Req Analyst - B. Sam
Designers - T. Book - M. Sosa
recruiting time
Programmers - new hire - new hire
Tester - M.Sosa
Pick the next best qualified candidate ?
9
Making Trade-off
  • What is/are the most important attribute(s)
    required to perform the task?
  • Does the candidate meet it/them?
  • What is/are marginally important attribute(s)
    needed to perform the task?
  • How many of them does the candidate meet?
  • What are the trade-off(s)?
  • Financial cost versus qualifications (think about
    the project goals)
  • Persons desire and career aspirations (think
    about the goals of project and the person)
  • Can anything else be modified --- such as task
    sequence or dates ?

10
Project Managers Decision on In-sourcing or
Out-sourcing
  • Large projects with enormous amount of effort and
    time required in human resource 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
often comes back to the bite us
11
Process and Task Methodology
  • 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 rules and principles to
    accomplish an activity
  • description of the rules the actual sub-steps
    that make up the procedure
  • description of the principle the intended
    goals of the methodology and why the procedure
    will achieve the goals

(Most do not have this)
12
Process and Tasks
  • What is the overall process?
  • What tasks should be included? And why?
  • Have we already considered this before and 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

13
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?
14
Methodology to Accomplish Major Tasks
  • Requirements Gathering, Analysis, and
    Representation is something we have talked about
    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

15
Methodology to Accomplish Major Tasks (cont.)
  • What about Implementation Task Methodology?
  • 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 ?

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

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

18
In Your (this classs) case
  • You have an end date thats 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 (cant outsource either! )
  • Goals
  • Tools
Write a Comment
User Comments (0)
About PowerShow.com