2010_SummerCourse_PM for Embedded Systems

Embed Size (px)

Citation preview

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    1/158

    ITSS PROJECTMANAGEMENT FOR

    EMBEDDED SYSTEMSchool of Information & Communication

    Technology Hanoi University of Science& Technology

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    2/158

    1. Introduction

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    3/158

    Masuda TeruakiEmail: [email protected]

    D Thanh BnhEmail: [email protected]

    Nguyn Hu Nam DngEmail: [email protected]

    mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]
  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    4/158

    1.1 Introduce yourself

    Your name

    Your company

    Your job

    Your goal in this course

    Your hobby

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    5/158

    1.2 What is Project?

    A project is a temporary work to create a unique product, service, or result.

    Temporariness : Project has a definite beginning andend.

    Uniqueness : Project has new elements for the team.

    So what?Project should be managed on the assumption that thechange would happen.

    Definition of Project

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    6/158

    Example of project

    System Development ProjectBuild a new stadiumIntroduce new process in the team

    Transfer the residentHosting party etc...

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    7/158

    1.3 What is Your Project?

    List up below the projects which you haveexperienced in your career.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    8/158

    Probability of project success

    What do you think the rate of IT project success?

    90% ?

    70% ?

    50% ?

    30% ?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    9/158

    Which is the successful project?

    Project A SystemDelivered the system by the date agreed on.Completed the project within budget.

    Almost never used after appreciation.

    Project B SystemMissed the deadline.Completed the project over budget.Has been used over 10 years.

    Which is the better project for you?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    10/158

    Was the Euro Tunnel Project success or failure?

    ( http://en.wikipedia.org/wiki/Channel_Tunnel )

    http://en.wikipedia.org/wiki/Channel_Tunnelhttp://en.wikipedia.org/wiki/Channel_Tunnel
  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    11/158

    1.4 Dimensions of project success

    Project Management Success

    Project Success

    Business Success

    FuturePotential

    Level 1

    Level 2

    Level 3

    Level 4

    The Layer of Project Success

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    12/158

    1.5 Project Life Cycle

    DesignPhase

    ProductPhase

    TestPhase

    Risks

    Cost for changeDeliverableDeliverable

    AnalysisPhase

    Deliverable

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    13/158

    Figure

    Phase in Which defect was fixed

    10

    20

    50

    100

    200

    500

    1000

    2

    1

    5

    Requirements Design Code Development Acceptance Operation test test

    Smaller Software Projects

    Larger Software Projects

    Median (TRW Survey) 80% 20%

    SAFEGUARD

    GTE

    IBM-SSD

    10

    20

    50

    100

    200

    500

    1000

    R e

    l a t i v e c o s

    t t o f i x

    d e

    f e c

    t

    2

    1

    5

    Requirements Design Code Development Acceptance Operation test test

    Richard W. Selby , Software Engineering: Barry W. Boehm's Lifetime Contributions to Software

    Development, Management, and Research P223

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    14/158

    Project Management is the applicationknowledge, skills, tools, and techniques toproject activities to meet the projectrequirements. (PMBOK)Project management includes generalmanagement skill and leadership as well.

    Although there are many personal element, wecan learn the way of project management as atechnical skills.

    1.6 What is Project Management?

    < Project needs Project Management >

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    15/158

    1.7 What is Leadership?

    Generally, leadership is the function to showthe goal and integrate people to achieve it.Leadership try to find out things in common.Leadership need to get the clear image of thefuture.Leadership focus on handling with complaintswhich can relate to hope and spirit.

    A good leader has always focused on thedesirable future to unify the team.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    16/158

    1.8 What is Management?

    Generally, management focus on(understand&control) the diversity of teammembers and complexity of tasks.

    Management try to see the different things asdifferent.The start point of management is in eachmember and each task.Management use the process of Plan Do Check Act which is called PDCA cycle.

    A good manager find out the specifics of eachmembers and make full use of these talent.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    17/158

    Cf. Leaders versus Managers

    LeaderFocus on futureIntegrationHopeVisionCreativeInspiringInnovativeOpportunistic

    ManagerFocus on presentDiversityWatchSupportProblem-solving

    AnalyticalStructuredRealistic

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    18/158

    1.9 Project Stakeholders

    Organization

    Quality Assurance

    ProjectSponsor

    Accountant

    Gr

    Group leader

    PM Team

    PM

    BusinessPartner

    Clients

    ManagerTop Management

    Team members

    End-users

    PMO

    Customer

    Fill stakeholder name in the blank circles.

    Sale Division

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    19/158

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    20/158

    1.11 Framework of Project Management

    Project Management Institute (PMI) publishedProject Management Body of Knowledge(PMBOK) as a project management standard. PMBOK will help all project to provide sharedframework and language for projectmanagement.

    PMBOK is current global standard in ProjectManagement (PM)PMBOK consists of the set of processes inpast project in various industries.

    < Framework as a PMBOK >

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    21/158

    Cf. Other framework of PM in the world

    PRINCE2 (Projects in Controlled Environments, 2ndversion) of United Kingdom.

    ICB (IPMA Competence Baseline) of International

    Project Management Association in Europe.

    P2M (Project & Program Management for enterpriseinnovation) of Japan

    Now, the workgroup, ISO/PC 236 is running to set anew international PM standard which is called ISO21500. (PMI in taking initiative in the WG.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    22/158

    1.12 Five Process Groups

    Initiation

    Planning

    Closing

    Executing

    Monitoring& Controlling

    Monitoring &Controlling includesall process groups

    Manage QCD with risks.

    PMBOK(R) grouped many project processes into five categories,Project Management Process Groups (or Process Groups):

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    23/158

    1.13 9 Knowledge Areas

    1. Project Integration Management2. Project Scope Management3. Project Time Management4. Project Cost Management

    5. Project Quality Management6. Project Human Resource Management7. Project Communication Management8. Project Risk Management9. Project Procurement Management

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    24/158

    1.14 Input - Tools & Technique - Output

    PMBOK use the process framework;Input Tools & Technique Output

    Input Tools& Technique

    Output

    - Activity List- Activity

    ResourceRequirements

    - Project ScopeRequirements

    - ExpertJudgment

    - AnalogousEstimating

    - ParametricEstimating

    - Reserve Analysis

    - ActivityDurationEstimates

    - Project

    DocumentUpdates

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    25/158

    1.15 Framework for Problem Solving

    < Constraint Condition > GoalObjective

    Plan

    Past (Cause) Present (Effect)

    Natural Disaster, World Recession, etc (Absolute)

    Law, Restricted Budget, Dead line, etc (Relative)

    Problem< Input >- Staffs- Products- Budget- Information

    etc..

    < Process >- Management Way- How to operate- Schedule- Sequence of task

    etc..

    Output

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    26/158

    Exercise

    < Constraint Conditions >Tight schedule, a lot of works,no additional resources etc.

    Sendproductscorrectly

    Past (Cause) Present (Effect)

    Problem< Inputs >- Two Staffs

    - Products- OrderInformation

    < Processes >- Send the products

    to ordered placeas soon aspossible with nocheck.

    Sent productsto in-correct

    place

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    27/158

    PMBOK Processes for problem solving

    Input Tools& Technique

    Output

    If you get thewrong input, theoutput should bewrong in correct

    process.Cf. Garbage in,

    garbage out.(GIGO)

    This partcorrespond tothe process.

    If you takeinefficientprocess, outputwill be poor.

    If there are somevariancesbetween the goaland the output,

    you have someproblem.

    Constraint conditions Goal

    Problem

    Past (Cause) Present (Effect)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    28/158

    2. Project Initiating

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    29/158

    2.1 Project Initiation2.1.1 Definition of Project Initiation(1)

    Project Initiation is the first process group inproject.You need to understand project goal.

    You may need to convince stakeholders.So, Project Charter is needed.You need to communicate well withstakeholders of the project.

    Good communication depend on theperception through shared experiences.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    30/158

    Output

    Definition of Project Initiation(2)

    Project Initiation is the process to beauthorized officially at the beginning of a newproject.

    Input

    Tools& Technique

    - Business Case- Enterprise

    Environmental

    Factors- Statement ofWork

    - OrganizationalProcess Assets

    - ExpertJudgment

    Project Charter

    1. Purpose

    2. Objectives3. Requirements4. Risks5. Milestone6. Budget

    :

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    31/158

    2.1.2 Make sure final project goal / purpose

    Project has several goals.Project is one of the measure of businessgoals. It is needed to understand therelationship between goal and measure.Please ask these questions as follows;

    What is the final goal of this project?What is the objectives in this project?

    What for? The best way to get these information is to goto client office and communicate directly.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    32/158

    2.1.3 Characteristics of Effective Goals

    Goals should be specific and writtenGoals should be quantitative not qualitativeGoals should be challenging yet achievable

    The set of goals should be mutually reinforcingGoals should focus on both ends and meansGoals should be time bound

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    33/158

    2.1.4 Goals Should Be SMART

    Specific

    Measurable

    Attainablebut Challenging Results Oriented

    Time bound

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    34/158

    If your supervisor asked you as follows, howdo you organize these goals?

    "Develop a new order-receiving and deliverysystem to achieve these goals.

    improve of customer satisfaction speed up the operational process make associates skilled up

    satisfy the QCD (Quality, Cost, Delivery) raise profit margin

    Exercise

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    35/158

    Sample Contents of Project Charter

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    36/158

    2.2 Identify Stakeholders

    Identify all people and organizations impactedby the project, and document relevantinformation regarding their interests,involvement, and impact on project success.

    Input Tools& Technique

    Output

    1. Project Charter2. Procurement

    Documents3. Enterprise

    EnvironmentalFactors

    4. OrganizationalProcess Assets

    1. Stakeholder Analysis

    2. ExpertJudgment

    1. StakeholderRegister

    2. StakeholderManagementStrategy

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    37/158

    Cf. Additional point

    Recognize constraint conditionsConstraint conditions restrict both inputs andprocesses

    Identify constraint conditions gives you;Policy of the projectCreativityPriorityNegotiation powerCustomer satisfaction

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    38/158

    3. Project Planning

    3 1 P j t Pl i

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    39/158

    3.1 Project Planning3.1.1 Overview

    Project Charter

    - Project Goal- Scope- Delivery time- Budget- Quality

    Integration

    Management

    Project Management Plan

    Scope Management Collect Requirements, Define Scope,Create WBS

    Time Management Define Activities, Sequence Activities,Estimate Activity Resources, Estimate

    Activity Durations, Develop Schedule

    Cost Management Estimate Cost,Determine Budget

    Quality Management Plan Quality

    Human ResourceManagement

    Human Resource Plan

    CommunicationManagementPlan Communications

    Risk Management Plan Risk Management, Identify Risk,Perform Qualitative/Quantitative Risk,Plan Risk Responses

    ProcurementManagement

    Plan Procurements

    Project Plan

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    40/158

    3.1.2 Importance of Planning (1)

    E x c e s s

    i v e

    C o s t

    ( %

    )

    Gred Githens, Financial Models, Right Questions, Good Decisions PM Network July 1998 Volime 12, Number7

    -50

    200

    5 10 15 200

    50

    100

    150

    Planning cost (%)

    The relationship between planning cost and excessive cost of 31 project in NASA

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    41/158

    2.7

    76.5

    7.3

    20.4

    11.9 14.1

    0

    10

    20

    30

    40

    50

    60

    7080

    0-5 (14PJ) 5-10 (8PJ) 10-15 (7PJ)

    Planning Cost

    Ecessive Cost

    Importance of Planning (2)

    Gred Githens, Financial Models, Right Questions, Good Decisions PM Network July 1998 Volime 12, Number7

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    42/158

    3.1.3 Develop Project Management Plan

    First of all, it is needed to develop projectmanagement plan.Project Management Plan is the plan for

    the way to manage your project whichincludes below but not limited to;Change management plan

    Configuration management planKey management reviews for content,extent, and timing to facilitate addressingopen issues and pending decisions.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    43/158

    3.1.4 How to execute management cycle?

    PLAN

    DO

    CHECK

    ACT

    The key to manage well is to run the basicmanagement cycle which is called PDCA asfollows;

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    44/158

    ProjectManagement

    Plan

    ScopeManagement

    Plan

    TimeManagement

    Plan

    CostManagement

    Plan

    QualityManagement

    Plan

    Human ResourceManagement

    Plan

    CommunicationManagement

    Plan

    RiskManagement

    Plan

    ProcurementManagement

    Plan

    3.2 Create Management Plan

    Plan the way tomanage each plan

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    45/158

    3.3 Collect Requirements

    The process of defining and documentingstakeholders needs to meet the project purpose.

    Project Charter

    1. Project background2. Project purpose3. Measurable objectives

    - Quality- Cost (Budget)- Delivery (Milestone)

    4. System configuration5. WBS6. Organizational chart7. Appendix

    RequirementsDocumentation

    1. Business needs2. Project purpose3. Project objectives4. WBS deliverables5. Product design

    6. Product development7. Test scenarios8. More detail

    requirements

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    46/158

    3.3.1 Interview skill

    Interview skill is the core skill in CollectRequirements.Generally, listening is hard work for person;

    Rush to actionSpeed difference: speaking 135-175 WPM, canlisten at 400-500 WPMLack of training

    So, you need to train the both skills foreffective collect requirements.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    47/158

    3.3.2. Basics of Interview Skill

    Open Question:Question which start from the words What,Why, Who, When, Where, How, How many,How much, How long? etc.

    Closed QuestionQuestion which start from the words Do you

    ?/Are you A closed question can be answered with either'yes' or 'no'.

    Combine these two questions to get moreinformation from your clients.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    48/158

    3.3.3 Active Listening

    Put the speaker at ease. Smile!Make eye contact, ask questions, take note.Show that you want to listen.Exhibit affirmative head nods and appropriate facialexpressions.

    Paraphrase Avoid interrupting the speaker. Dont over talk! Use the starter question when you start the interview.

    Has business been busy today?May I ask a question now?

    Yes-Taking Question: Ask question what the answershould be yes to make the atmosphere positive. We set the dead line at the end of next month at thelast meeting, wasnt it? Yes , we did.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    49/158

    3.4 What is Scope?

    Scope means range" of the products orservices in a project.

    What tomake?

    What todo?

    Project

    Web Site SystemID Management FunctionConfirmation Mail Function

    etc

    Make PM PlanManage QualityWrite a Final Report etc

    Product Scope

    Project Scope

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    50/158

    3.4.1 Scope Management Planning

    As scope is quite important for the project, scopeshould be managed throughout the project.Scope can be changed little by little in a project, whichis called Scope Creep. To avoid it, you need to plan the process of changemanagement.It is safe to suppose that scope will change duringproject. So, scope management plan need to have theprocess

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    51/158

    3.5 Create WBS(1)

    WBS (Work Breakdown Structures) is a systematicstructure which is break-downed the project deliverablesand processes.

    1 Project Management1.1 Planning

    1.1.1 Scope Statement1.1.2 Activity List

    1.1.3 Resource Plan1.1.4 Time Estimate1.1.5 Cost Estimate1.1.6 Risk Analysis1.1.7 Schedule1.1.8 Project Management Plan

    1.2 Executing2 Design

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    52/158

    New System

    PM

    Sub-System1

    Level 0

    Level 1

    Level 2

    Level 3

    100

    Rule

    Work Package WP)

    System

    TransferDevelopment

    Sub-System2

    Create WBS(2)

    0

    1 2 3

    3.1 3.2

    Testrogrammingeviewesign3.2.43.2.1 3.2.2 3.2.3

    Decomposition

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    53/158

    New System

    Sub-system1

    TestrogrammingTest

    Specification

    Development Migration

    Sub-system2

    Level of Work Package depends on the purpose.

    Can youunderstand

    the elements of

    WBS?How often do youcheck progress?Is it clear divisionof roles?

    Does work packageneed more accurateestimation?

    DevelopmentAssistance

    Design

    0

    1 2 3

    2.1 2.2

    2.2.1 2.2.2 2.2.3 2.2.4

    Create WBS(3)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    54/158

    3.6 Develop Schedule

    Define Activities

    Estimate ActivityDurations

    Develop

    Schedule

    Plan RiskManagement

    Estimate Activity

    Resources

    Sequence Activities

    EstimateCosts

    DevelopHuman

    ResourcePlan

    PlanQuality

    DetermineBudget

    DefineScope

    CreateWBS

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    55/158

    3.6.1 Overview

    Define Activities

    Sequence Activities

    Estimate Activity Duration

    Develop Schedule

    Estimate Activity Resources

    Integration Management

    Estimation

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    56/158

    3.6.2 Define Activities

    Order-receiving

    system

    SystemStructure

    Design

    ProgramStructure

    Design

    WBS

    Feedback the

    change to WBS

    System Development

    Sub-system Activity 1 Activity 2

    Order-receiving

    system

    SystemStructureDesign

    Analysis

    Design

    Review

    UserInterface

    Design

    Analysis

    Design

    Review

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    57/158

    3.6.3 Sequence Activities

    Identify and document relationships amongthe project activities.

    Input Tools& Technique

    Output

    1. Activity List2. Activity

    Attributes3. Milestone List4. Project Scope

    Statement5. OrganizationalProcess

    Assets

    1. PrecedenceDiagrammingMethod (PDM)

    2. DependencyDetermination

    3. Applying Leadsand Lags

    4. ScheduleNetworkTemplates

    1. ProjectScheduleNetworkDiagrams

    2. Project

    DocumentUpdates

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    58/158

    3.6.4 Precedence Diagramming Method (PDM)

    Describe the activity as a node and connect it withthe other using allow to express sequencerelationship. PDM can describe four dependentrelationships. Finish to Start (FS) The initiation of the successor activity depends on

    the completion of the predecessor activity. Finish to Finish (FF) The completion of the successor activity depends

    on the completion of the predecessor activity.

    Start to Start (SS) The initiation of the successor activity depends onthe initiation of the predecessor activity.

    Start to Finish (SF) The completion of the successor activity dependson the initiation of the predecessor activity.

    A

    B

    A

    B

    A

    B

    A

    B

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    59/158

    3.6.5 Dependency Determination

    To define the sequence among the activities,three types of dependencies are used;1. Mandatory Dependencies:

    Dependencies that are contractually requiredor inherent in the nature of the work.

    2. Discretionary Dependencies:Dependencies which can be determined

    sequence of activities discretionary.3. External Dependencies:

    Dependencies that are controlled by outsider.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    60/158

    3.6.6 Estimation

    Collect Requirements

    Size

    Productivity

    Worker-hour

    Duration

    Cost

    Scope of estimation

    Objectives of

    estimation

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    61/158

    (1) Sizing

    Collect Requirements

    Size

    Scope of estimation

    < Examples of Metrics >Number of requirementsNumber of steps (LOC: Lines of code)Number of functions (FP: Function point)Number of pagesNumber of I/ONumber of interface

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    62/158

    (2) Estimate Productivity

    How to estimate the productivity?

    Productivity means the amount of output perhour/day/month.To get the productivity, the past data are used.Over 30 data are desired to get the reliableaverage productivity. (You need to modify itdepends on the skill level of team members.)

    SizeProductivity

    Worker-Hour

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    63/158

    (3) Estimate Worker-Hour

    After you estimate the size and productivity,you can calculate worker-hour using theformula.

    Size

    Productivity

    Worker-Hour

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    64/158

    (4) Estimate Activity Duration

    Number ofWorkers

    Duration Worker-Hour

    Estimate Activity Durations is the process of

    approximating the number of work periodsneeded to complete individual activities withestimated resources.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    65/158

    (5) Estimation Framework

    Phase

    BusinessTalks CollectRequirement SystemDesignType of

    Estimate Order-of-

    magnitude

    estimate

    Preliminaryestimate

    Definitiveestimate

    Tools and

    Techniqueof

    Estimating

    Top-Down Estimating

    Parametric Estimating

    Bottom-Up Estimating

    Accuracy

    Estimation

    30 50 15 30 5 15

    3 7 C i i l P h M h d

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    66/158

    3.7 Critical Path Method

    Based on the estimated duration, calculatethe theoretical Early Start and Early Finishdates, and Late Start, Late Finish dates.The critical path is the longest path

    throughout the project. The float of criticalpath should be zero.Project manager have to focus on the criticalpath to manageCritical path can change to the other path in aproject. So, project manager need to monitornear-critical path as well.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    67/158

    Exercise : Critical Path Method

    A 12

    B 8

    C 6

    D 11

    E 10

    F 7

    H 5

    G 9

    I 4

    J 3

    Calculateshere

    ES EF

    1 12

    13 20

    13 1819 25 26 34

    19 28

    21 31

    ActivityPredecessor

    activitySuccessor

    activityDuration

    EarlyStart

    EarlyFinish

    LateStart

    LateFinish

    TotalFloat

    12 1 12 8 13 20

    6 13 18

    11 21 31 10 19 28

    7 19 25 9 26 34

    5 4 3

    3 8 C iti l Ch i

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    68/158

    3.8 Critical Chain

    Critical Chain is the method of shorten theproject duration.

    A:

    B:

    7 Days

    14 Days

    5 Days

    ?

    Task Buffer

    5 Days

    10 Days

    Project Buffer A:

    3 9 D l M t S h d l

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    69/158

    Process

    4 5 6 7 8 9 10 11

    Event Server Client

    Meeting

    Training for user

    Requirement Definition Program Design

    Delivery

    Personnel 6 6 6 6 8 8 8 6

    Review

    Master ScheduleDate 20XX,Mar,25Planner xx Div) VinhDuration 20XX,Apr,1 20XX,Nov,30 8months

    System Development Project for X cop.

    Test Planning

    Note

    System Analysis

    Interface Design

    System Design

    Program Design

    ProgrammingProgram Test

    Integration Test

    Operation Test

    System Test

    3.9 Develop Master Schedule

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    70/158

    3.10 Estimate Activity Resources

    Estimate the type and quantities of material,people, equipment, or supplies required toperform each activity.

    Input Tools

    & TechniqueOutput

    1. Activity List2. Activity

    Attributes3. Resource

    Calendars4. Enterprise

    EnvironmentalFactors

    5. OrganizationalProcess

    Assets

    1. ExpertJudgment

    2. Alternatives Analysis

    3. PublishedEstimating data

    4. Bottom-UpEstimating

    1. ActivityResourceRequirements

    2. ResourceBreakdownStructure

    3. ProjectDocumentUpdates

    3.11 Cost Planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    71/158

    3.11.1 Cost ScheduleEstimate Costs

    The process of developing an approximation ofthe monetary resources needed to completeproject activities.

    InputTools

    & Technique Output

    1. ScopeBaseline

    2. HumanResourcePlan

    3. EnterpriseEnvironmentalFactors

    1. ExpertJudgment

    2. AnalogousEstimating

    3. ParametricEstimating

    4. Bottom-UpEstimating

    5. Three-PointEstimates

    1. ActivityCostEstimates

    2. Basis ofEstimates

    3. ProjectDocumentUpdates

    d

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    72/158

    3.11.2 Determine Budget

    Determine BudgetThe process of aggregating the estimated costsof individual activities or work packages toestablish an authorized cost baseline.

    Input Tools& Technique Output

    1. Activity CostEstimates

    2. ScopeBaseline

    3. ProjectSchedule

    4. ResourceCalendars

    5. Contracts

    1. Cost Aggregation

    2. Reserve Analysis

    3. Expert Judgment4. Historical

    Relationships5. Funding Limit

    Reconciliation

    1. CostPerformanceBaseline

    2. ProjectFundingRequirements

    3. ProjectDocumentUpdates

    3 12 Quality planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    73/158

    3.12 Quality planning

    Quality planning based on process and result.Test is important, but process design andmonitoring are more important.

    Input Tools& Technique

    Output

    1. Scope Baseline2. Cost Performa-

    nce Baseline

    3. ScheduleBaseline4. Risk Register5. Environmental

    Factors6. Process Assets

    1. Cost-Benefit Analysis

    2. Cost of Quality

    3. Control Charts4. Benchmarking5. Design of

    Experiments6. Statistical

    Sampling

    1. Quality Mana-gement Plan

    2. Quality

    Checklists3. Process Impro-vement Plan

    4. Quality Metrics5. Project Docu-

    ment Updates

    Sample Quality Planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    74/158

    Sample Quality Planning

    HTML Cording Guidline

    Items Basic Rules Changed

    OverallRule of file

    name

    Usable caracter : 0-9, a-z, A-ZDon't use number and under bar ( _ ) at the top of file name.

    Items Basic Rules Changed

    File name Name the easy file name to know the contents ata sight.

    VerificationScope

    Over WindowsXP and InternetExplorer6,Mac OS10.4 and Forefox 2.0

    Link Standardize the type of path (relative orabsolute)

    Javascript It is prohibited to write javascript in HTMLdirectly. Use external file.

    Files

    HTML

    HTML Cording

    Overall

    Exercise : Plan quality in your job

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    75/158

    Exercise : Plan quality in your job

    Items Basic Rules

    Items Basic Rules

    Ovreall

    3 13 Human resources planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    76/158

    3.13 Human resources planning

    Identify and document project roles,responsibilities, and required skills, andcreating a staffing management plan.

    InputTools

    & Technique Output1. Activity Resource

    Requirements2. Enterprise

    EnvironmentalFactors

    3. OrganizationalProcess Assets

    1. OrganizationCharts andPositionDescriptions

    2. Networking3. Organizational

    Theory

    1. HumanResource Plan

    Staff acquisition Resource calen-

    dars Staff release plan Training needs Recognition &

    rewards

    3 14 Communication Planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    77/158

    3.14 Communication Planning

    Customer satisfaction depends on the qualityof communication. At first, stakeholder analysis is needed.

    How about the knowledge and skills?Who is the key person?

    Are there any hidden stakeholders like topmanagement, other divisions staff.

    Plan Communications

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    78/158

    Plan Communications

    The process of determining the projectstakeholder information needs and defining acommunication approach.

    Input Tools& Technique Output

    1. StakeholderRegister

    2. StakeholderManagementStrategy

    3. EnterpriseEnvironmentalFactors

    4. OrganizationalProcess Assets

    1. CommunicationRequirements

    Analysis2. Communication

    Technology3. Communication

    Models4. Communication

    Methods

    1. CommunicationManagementPlan

    2. ProjectDocumentUpdates

    Sample of Communication Plan

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    79/158

    Sample of Communication Plan

    No Meeting Type Purpose Frequency Host Attendance

    1

    Phase Meeting DecisionMaking

    Anytime inneeded

    Client Client,PM,Sales

    2

    Team Meeting Progress Assessment

    Once in aweek

    PM PM,Projectmembers

    3

    MorningMeeting

    Know eachother, goodcommunica-tion

    Everymorning

    PM PM,Members

    Exercise

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    80/158

    Exercise

    In this project, we will use e-mail as a main tool for communication. Thepurposes of using e-mail are as follows; 1) Distribute informationaccurately, 2) Record the information, 3) Avoid interruption

    < The Rule when you send a mail>

    < The Rule when you reply a mail>

    < The Rule when you transfer a mail>

    < The Rule when you send a mail using bcc.>

    < Make the rule of how to use e-mail >

    3.15 Risk Planning

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    81/158

    3.15.1 Definition of Risk

    What is a risk?Uncertainty which will be able to make a goodor bad impact on the project.Project includes a lot of risk.

    You need to proceed almost all process in theproject considering risk.

    Mini Question

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    82/158

    Mini Question

    How to deal with the risk as follows;You plan to have a home party next weekend.But you dont know how many people will come. Now, you consider to prepare drink and food for10 people.It will be too much if you have only 5 people.It will be too small if you have 15 people.

    But you cant confirm how many people willcome in advance. (Uncertainty will be kept.)Please find out the best way to avoid the riskunder uncertainty.

    3 15 2 Whole process of Risk Management

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    83/158

    3.15.2 Whole process of Risk Management

    (2)IdentifyRisks

    (3) Risk Analysis

    Quantitative

    Qualitative

    (4) Plan RiskResponses

    Project Plan

    Risk Plan

    (5) Monitor and Control RisksResponses Plan still work?Are there any new risks?Do your risks changed?

    etc..

    (1) Risk Management Plan

    Managerepeatedly !

    Plan at first

    3 15 3 Risk management plan

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    84/158

    3.15.3 Risk management plan

    Plan Risk ManagementThe process of defining how to conduct riskmanagement activities for a project.

    1. RestraintConditions

    2. Scope Statement3. Schedule/Cost

    ManagementPlan

    4. CommunicationPlan5. Organizational

    Process Assetsetc..

    PlanningMeeting

    and Analysis

    Risk Management Plan

    MethodologyRoles and

    responsibilitiesBudgeting

    TimingRisk categories

    3 15 4 Identify Risks

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    85/158

    3.15.4 Identify Risks

    Determining the risks which may affect theproject and document their characteristics.Category

    SisRisk Driver Risk

    System Request is unclear. It may be delay to fixrequirement.

    Size of system is big. Estimation may be difficult.

    Quality requirement is high. It may be schedule delay.

    Technical Use new technology. It may take many time for troubleshooting.

    Use package software. It can be difficult to customize it.

    Organization

    End use cant join the project. It can be difficult to cover allusers needs.

    There are not enough systemengineer in the project.

    The project can be delayed.

    3 15 5 Perform Risk analysis

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    86/158

    3.15.5 Perform Risk analysis

    Probability

    High Many times occurred in the past

    Middle Several times occurred in the past

    Low Never or few times occurred in the past

    Impact Level

    High

    Company have to deal with it.( Lose all profit, Bring lawsuit, Have a press conference for appology etc.. )

    MiddleOther project team or divisionneed to help the project tosolve the problem.

    LowProject team or members cansolve ploblems using their ownbaffer.

    Big Middle Small

    High A B

    Middle A C

    Low B C

    ImpactProbability

    3 15 6 Plan Risk Responses

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    87/158

    3.15.6 Plan Risk Responses

    Plan Risk Responses is the process ofdeveloping options and actions to enhanceopportunities and to reduce threats to projectobjectives.

    Avoid

    Transfer

    Mitigate

    Accept

    Risk Management Plan

    Risk registerRisk-Related ContractDecisionsContingence PlanNew RiskRisks which areremained.

    RiskManagement

    Plan,

    Risk Register

    3.16 Procurement Planning3 16 1 Pl P

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    88/158

    3.16.1 Plan Procurements

    Procurement planning start from make or buyanalysis. It your project decide to buy, you need to meetwith good seller.

    The basic measure to do so is to make thedocument like Request For Proposal (RFP).

    RFP is nearly equal document to ProjectCharter which includes project goal, output,budget, and due date for provable seller.

    3 16 2 How to manage procurement risk?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    89/158

    3.16.2 How to manage procurement risk?

    Contract Types determine the risk which isshared between the buyer and seller.Project manager need to understand the basicspecification of contract types as follows;

    FFP FPI CPIF CPFF

    Sellers Risks

    Buyers Risks

    High

    HighLow

    Low

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    90/158

    4. Project Executing

    4.1 Project Executing4 1 1 Di t d M P j t E ti

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    91/158

    4.1.1 Direct and Manage Project Execution

    Perform the work defined in the projectmanagement plan to achieve the projectsobjectives.

    Project Plan Execute

    Output

    1. Deliverables2. Work performance

    information3. Change request4. Project

    management planupdates

    5. Project documentupdates

    4 1 2 Perform Quality Assurance

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    92/158

    4.1.2 Perform Quality Assurance

    High quality output will come from goodprocess.Perform quality assurance use audit to makesure the planned process is executed

    appropriately.Audit to theprocess

    Enhance the Review

    Process standards

    ProcessImprovement

    indicateQuality Process

    4.2 Team Building4 2 1 A i P j t T

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    93/158

    4.2.1 Acquire Project Team

    Confirm human resource availability andobtain the team necessary to complete projectassignments.If it is clear that the human resources are not

    enough to execute, project manager have toexplain about it to project sponsor.Project manager need to have the negotiationto get additional staff.

    4 2 2 Develop Project Team

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    94/158

    4.2.2 Develop Project Team

    Improve the competencies, team interaction,and the overall team environment to enhanceproject performance.Project manager should acquire skills to

    identify, build, maintain, motivate, lead, andinspire project teams to achieve high teamperformance and to meet the projectsobjectives.

    4 2 3 Team Building Activities

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    95/158

    4.2.3 Team Building Activities

    Forming Team meets and learn about the project and what theirformal rules and responsibilities are.

    StormingTeam begins to have different opinion and address theproject work, technical decisions, and PM approach.

    NormingTeam members begins to understand and adjust workstyle and behaviors.

    PerformingTeam reach the performing stage function as a well-organized unit.

    AdjourningTeam completes the work and moves on from theproject.

    4 2 4 Manage Project Team

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    96/158

    4.2.4 Manage Project Team

    "Project team organization" secures humanresources necessary for the completion of theproject. Tracking team member performance,

    providing feedback, manage conflict, keepperformance better.

    4.2.5 How to get better performance?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    97/158

    g pComulativenumber

    Base Line Intervention

    Record of comulative number of two teaching assistant work planned/performed

    32

    28

    24

    20

    16

    12

    8

    4

    1 2 3 4 5 6 7 8 9 10 11 12 13

    32

    28

    24

    20

    16

    12

    8

    4

    1 2 3 4 5 6 7 8 9 10 11 12 13

    Number of work planned Number of work performed

    Student A

    Every week meeting

    Week

    Week

    Student B

    How to get better performance? (cont)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    98/158

    g p ( )

    Able Leader A Not Able Leader B

    Not Able Leader C40 D : Direction

    C : Check F : Feedback

    Clear message Unclear message

    50 second 30 second

    50 second

    20

    0 10 20 30

    40 0 100 10 20 30

    D

    C

    F

    D

    C

    F

    D

    C

    F

    4.3 Basic Group Concepts

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    99/158

    p p

    RolesNorms and conformityMotivation managementGroup sizeGroup cohesivenessConflict managementInformal communications

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    100/158

    4.4.2 Conditions for creating motivation

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    101/158

    4.4.2 Conditions for creating motivation

    Motivation is the process that triggers and sustainsgoal-oriented behavior and the function of it.

    IncentiveDrive Sustained

    Needs,motives(internalfactors)

    Purposes,

    goals(externalfactors)

    B = P S* B: BehaviorP: PersonalityS: Situation

    Motivation

    4.4.3 Motivation types

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    102/158

    4.4.3 Motivation types

    The two types of motivation are intrinsic motivation and extrinsic

    motivation. Each can transform into the other.

    Intrinsic motivation Extrinsic motivation

    Focal point P (personality) S (situation)

    Orientation Process-oriented Result-oriented

    Merits Sustainable Easy to get, instant

    Demerits Difficult, takes time Not sustainable

    B = P S Each can transform intothe other.

    4.4.4 Carrot-and-stick or participatory approach?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    103/158

    4.4.4 Carrot and stick or participatory approach?

    1. People usually do not like work and, whenever possible, will attempt to avoid it.2. Most people must be coerced, controlled, ordered, or threatened with punishment

    to obtain their best performance.3. People usually will avoid responsibilities, place security first, and display little

    ambition.

    Theory X assumptions

    1. Normally, people view physical and mental effort at work is as natural as rest or play. 2. External controls and threats are not the only means of motivation.

    3. Motivation depends on the rewards, including the most important rewards satisfying ego needs or fulfilling needs for self-actualization.4. People usually are willing to take responsibility, given the appropriate conditions.5. Each company has a pool of creativity, which is necessary for problem-solving, in

    most of its workforce.

    Theory Y assumptions

    4.4.5 Types and hierarchy of needs

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    104/158

    4.4.5 Types and hierarchy of needs

    Self-actualization

    Esteem

    Love and belonging

    Safety

    Physiological P r i m a r y n e e

    d s

    ( P h y s

    i o l o g

    i c a

    l n e e

    d s )

    S e c o n d a r y n e e

    d s

    ( S o c i a

    l m o

    t i v e s )

    Desire for foodand sleep

    Avoidance ofuncertainty

    Desire for friendship and tobelong to group

    Desire for recognition andrespect

    Full commitment to realizing one'sown potential through goals

    4.4.6 Understanding social motives

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    105/158

    g

    (1) Trying the challenge of moderately difficult tasks(2) Asking for feedback after an event(3) Taking responsibility for one's own decisions(4) Thinking the cause of a failure is insufficient personal effort(5) Tending to select colleagues based on capability instead of familiarity

    Achievement needs

    (1) Frequently making phone calls or sending e-mail(2) Making a lot of eye contact for a friendlier atmosphere(3) Often seeking approval from others in one's actions(4) Responding very negatively to those with different opinions(5) Easily feeling more anxious when evaluated by others(6) Tending to select colleagues based on familiarity instead of capability(7) Showing higher performance in group work, and effectively

    displaying one's ability by working cooperatively to give feedback

    Affiliation motives

    4.4.7 Expectancy-Value theory

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    106/158

    p y y(1) Setting attractive goals

    Motivation Expectedchanceof success

    Attractivenessof goal

    =

    Motivation depends on the expected chance of success, which issubjective, and the attractiveness of the goal.

    Vroom's expectancy theory

    - Associated with ahigher-level goal

    - May need a worthycause

    Breaking down a goalinto smaller and moreconcrete goals raises the"expected chance ofsuccess," a subjectivevalue.

    4.4.7 Expectancy-Value theory (cont)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    107/158

    (2) Setting goals at pertinent levels

    Achievementbehavior

    Achievementneed

    Probability ofsuccess

    Attractivenessof goal= ( )

    The best achievement behavior is obtained at a 50% probability ofsuccess for the goal. (It is important to set a goal that is moderatelydifficultneither too easy nor too hard.)

    Atkinson's theory of achievement motivation

    0.2 0.8 = 0.160.3 0.7 = 0.210.4 0.6 = 0.240.5 0.5 = 0.250.6 0.4 = 0.24

    .

    .

    Maximum

    p y y ( )

    4.4.8 Raising intrinsic motivation

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    108/158

    g

    Intrinsic motivation increases depend on the "feeling ofcompetence" and "feeling of autonomy."

    Cognitive evaluation theory

    Intrinsicmotivation

    Competence AutonomyFeeling ofaccomplishment

    4.4.9 Gaining a feeling of accomplishment,depending on causal attribution

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    109/158

    p g

    A. I neglected costmanagement.

    C. It was inherentlyimpossible to do theproject for less than$10,000.

    D. Luck was not on myside this time.

    B. I am always tooeasygoing.

    Suppose you were the project manager in charge of a project withplanned development costs of less than $10,000. However, costsexceeded the planned amount by $10,000. What was the cause?

    Answer this question intuitively.

    4.4.10 Gaining a feeling of accomplishment in a process-oriented approach

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    110/158

    p pp

    Small goal

    Success!

    Small goal

    Success!

    Feeling ofaccomplishment

    By breaking down a goal into more detailed goals, you can

    experience the feeling of accomplishment many times andraise intrinsic motivation.

    Feeling of

    accomplishment

    4.5 Conflict Management4.5.1 Definition of Conflict

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    111/158

    4.5.1 Definition of Conflict

    Conflict is a form of interaction among partiesthat differ in interests, perceptions, andpreferences.

    A process that begins when one party perceives

    that the other has negatively affected, or isabout to negatively affect, something that he orshe cares about.

    4.5.2 Sources of Conflict

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    112/158

    Differences between interfaces in:

    Values - moral, ideological, or philosophical outlookRole Pressures - associated with each position is the set ofactivities and expected behaviorsStatus ConflictPersonality DifferencesOrganizational Structure - overlapping functions, unclearresponsibilitiesCultural DifferencesPerceptions

    GoalsExpectationsDeficient information that causes misunderstandings

    Ambiguity when there are power or turf strugglesCompetition over scarce resources

    4.5.3 Causes of Conflict in Organizations

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    113/158

    g

    Organizational StructuresSpecialization and DifferentiationGoal differencesScarce/shared resourcesMultiple authority relationshipsPolicies and proceduresRewards

    Situational ForcesDegree of interaction/interdependenceNeed for consensusStatus differencesCommunication

    Ambiguous responsibilities

    4.5.4 Consequences of Conflict (1)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    114/158

    Positive ConsequencesLeads to new ideasStimulates creativityMotivates changePromotes organizationalvitalityHelps individuals andgroups establish identitiesIncreases group

    cohesivenessServes as a safety valve toindicate problems

    Forces articulation of views andpositionsResults in greater clarification ofissuesResults in greater understanding ofissues and individualsMakes values and belief system ofthe organization more visible andconcreteEasier to see organizationalpriorities

    Consequences of Conflict (2)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    115/158

    Negative ConsequencesDiverts energy from workThreatens psychologicalwell-beingWastes resourcesCreates a negative climateBreaks down groupcohesionCan increase hostility andaggressive behaviors

    Dysfunctional conflictreduces:ProductivityMoraleJob satisfaction

    Dysfunctional conflictincreases:

    Anxiety Absenteeism

    Turnover

    4.5.5 Characteristics of Conflict

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    116/158

    Behavior typical of conflict situationsStereotypingOvervaluation of ones own group Devaluation of the other group

    Polarization on the issuesDistortion of perceptionsEscalation

    4.5.6 Five Conflict Handling Styles

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    117/158

    A s s e r t i v e n e s s

    A s s e r t i v e

    U n a s s e r t

    i v e

    CooperativenessCooperativeUncooperativeness

    Compromising

    Avoiding

    Competing ColWorkerating

    Accommodating

    4.5.7 Conflict Resolution Styles

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    118/158

    Avoiding : Recognizing the conflict exists , but react bywithdrawing from or suppressing the conflict. Use whenthe issue is trivial; when you perceive no chance ofsatisfying your concerns; to let people cool down andgain perspective; and when others can resolve the

    conflict more effectively.Dominating: (Competing) When one party seeks toachieve certain goals or to further personal interests,regardless of the impact on the parties to the conflict,

    he or she competes and dominates. Use when quickdecisive action is vital.

    Conflict Resolution Styles (con.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    119/158

    Compromising: When each party to the conflict must

    give up something, sharing occurs, resulting in acompromised outcome. Use when goals are importantbut not worth the effort of potential disruption of moreassertive approaches.

    Integrating: (ColWorkerating) When each of theparties in conflict desires to satisfy fully the concern ofall parties, there is cooperation and the search for amutually beneficial outcome. Use to find an integrativesolution when both sets of concerns are too importantto be compromised.

    Conflict Resolution Styles (con.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    120/158

    Obliging: (Accommodating/Smoothing) Placing the

    opponents interest above your own. Use when you findyou are wrong; when issues are more important toothers than yourself; to build social credits for laterissues; to minimize loss when you are outmatched and

    losing; and when harmony and stability are important.

    4.5.8 Group Conflict

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    121/158

    Group conflict is related to the effects of group

    membership on individual behaviorTendency to believe whatever is believed in astrong reference group believeGroups individuals strongly identify with tend toaffirm them in important waysWith acceptance by group however comesexpectations

    To conform to values and behaviors acceptable tothe group

    4.5.9 Resolving Team Conflicts

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    122/158

    Promptly let the people involved know how their conflict is

    affecting performance.Set up a joint problem-solving approach to resolve theconflict.

    Ask the people involved to present their viewpointsobjectively.Get agreement on the problem that needs to be solved.Have each person generate possible solutions.Get commitment on what each person will do to solve theproblem.Summarize and set a follow-up date to make sure theconflict has been resolved.

    4.5.10 Some Interpersonal Skills Used in Managing Teams

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    123/158

    Ask appropriate questions to stimulate ideas anddiscussionListen closely and intently to ideas and concernsManage group discussions to encourage

    everyone to participateEstablish an informal and non-threateningclimate to stimulate open discussionUse the consensus method to reach decisionson key issues

    Some Interpersonal Skills Used in Managing Teams (con.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    124/158

    Involve team members in setting goalsImplement meeting guidelines to minimizewasted time in meetingsEncourage respect so all know their contributions

    are valuedDeal with dysfunctional behaviors immediatelyCelebrate the achievement of milestones andaccomplishmentsUse recognition, assignments and othertechniques to motivate team members

    4.5.11 Guidelines for Achieving Consensus

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    125/158

    Avoid arguing for your own rankings. Present your

    position as lucidly and logically as possible, but listen tothe other members reactions and consider themcarefully before you press your point.Do not assume that someone must win and someone

    must lose when discussion reaches a stalemate.Instead, look for the next-most-acceptable alternativefor all parties.Source: Decisions, Decisions, by Jay Hall, Psychology Today, 11/71

    Guidelines for Achieving Consensus (con.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    126/158

    Do not change your mind simply to avoid conflict and to

    reach agreement and harmony. When agreementseems to come too quickly and easily, be suspicious.Explore the reasons and be sure everyone accepts thesolution for basically similar or complementary reasons.Yield only to positions that have objective and logicallysound foundations.

    Guidelines for Achieving Consensus (con.)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    127/158

    Avoid conflict-reducing techniques like coin-flips,

    majority votes, averages, and bargaining. When adissenting member finally agrees, dont feel that hemust be rewarded by having his own way on some laterpoint.

    Differences of opinion are natural and expected. Seekthem out and try to involve everyone in the decisionprocess. Disagreements can help the groups decisionfor a wider range of information and opinions increaseschance that the group will hit upon more adequatesolutions.

    4.5.12 Resolving Conflict

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    128/158

    C: Clarify the Issue the most important step A: Address the Problem: Have a strategy foraddressing the conflictL: Listen to the other side

    M: Manage you way to resolution

    4.5.13 Amelioration of intergroupdiscrimination

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    129/158

    Summer camp experiment

    (1) They interacted as two separate groups.(2) The groups competed in sports and

    games, arousing feelings of competition.

    (3) An emergency that required a concertedeffort by the two groups (failure in thewater supply system) was created. Then ,the groups had to solve the problem.

    Nasty relationship due to hostilityand conflict

    1 2 3 4 5Friendly

    20

    40

    C h i l d r e n

    i n e a c h g r o u p (%)

    Group A

    Group B

    Intergroup discrimination ameliorated asboth group became friendly with each other

    1 2 3 4 5

    20

    40

    (%)

    Group A

    Group B C h i l d r e n

    i n e a c

    h g r o u p

    Introducing a superordinate goal that can be achieved onlywith a concerted effort by the groups was effective inameliorating the intergroup discrimination or conflict.

    Not friendly

    FriendlyNot friendly

    4.6 Assertive communication4.6.1 Assertiveness

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    130/158

    Communication in which people convey their own feelings or thoughtswhile respecting the feelings and thoughts of others (where allcommunicating parties are considered important)

    Three communication types in assertion theory

    I'm sorry to have to bother you with this, but please reviewall 50 pages of this manual by the end of the day.

    - Non-assertive : All right... (Oh man, this is too much. I mayhave to work through the night.)

    - Assertive : If I review the manual, I won't be able tocomplete the report that is due today. Which job should getpriority?

    - Aggressive : This request is too sudden, and I can't handleit! I've got a lot of other work on my plate so I'm really busy.It's definitely impossible for me to do!

    Projectleader

    Teammember

    4.6.2 Assertiveness training

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    131/158

    DESC method

    For problem resolution, this method organizes in advancethe contents of communication from the followings:

    D (Describe) : Describe the situation objectively. E (Explain) : Express your opinion with regard to D,

    and explain the effects subjectively. S (Specify) : Suggest a solution or compromise. C (Choose) : State a positive option (agree) and

    negative option (disagree) for thesuggestion, and the actions for eachoption.

    4.6.3 Example

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    132/158

    Suppose that one of the people attending a meeting has kept

    talking to express his opinions.

    Mr. XX, you've been talking for 15 minutes since the start of the meeting. (D)

    I need about 5 minutes for my progress report. Now, looking at the time leftfor the meeting, I may not be able to report my progress. Besides, Mr. YYalso needs to present his report. (E)

    So, I suggest Mr. XX make a report individually to the project leader. (S)

    If we do so, the two of us giving reports can do so within the specified time.(C for a positive option as the result)If the individual reporting is going to be inconvenient, will you pick and reportonly the main points? (C for a negative option as the result)

    4.7 Distribute Information

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    133/158

    Distribute information is the process of makinginformation available to project stakeholders ascommunication plan.Distribute information is the key to build a good team.

    Main element as a team is that team has regular

    communication each other.If you distribute information correctly, team membereasy to get the feeling as a team.It is not good to distribute information to some members

    only except delicate information.It is more effective to share bad news between teammembers as soon as possible to get their support.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    134/158

    Project Monitoring &Controlling

    5.1 Project Monitoring & Controlling5.1.1 Overview

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    135/158

    The process of tracking, reviewing, and regulating theprogress to meet the performance objectives definedin the project management plan.

    Input Output1. Project Manage-

    ment Plan2. Performance

    Reports

    3. EnterpriseEnvironmentalFactors

    4. OrganizationalProcess Assets

    Expert Judgment

    1. Change Requests2. Project Manage-

    ment Plan Updates3. Project Document

    Updates

    5.1.2 Verify Scope

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    136/158

    The process of formalizing acceptance of thecompleted project deliverables.

    Document

    Software

    Inspection

    Accepted

    Document

    Software

    5.1.3 Control Scope

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    137/158

    The process of monitoring the status of the project andproduct scope and managing changes to the scopebaseline.

    The content of the process is as follows.(1) Project manager understands the change request(2) Assess the impact of variation from scope baseline.(3) Reflect scope change to the schedule, cost plan,

    quality plan etc. WBS also should be changed .

    Sample Form of Change Request

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    138/158

    Sample Form of Change Log

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    139/158

    For effective change control, it is needed to use

    change log sheet.

    ChangeID

    DateSubmitted

    Cost /Schedule

    Impact

    Requestedby:

    Description Status

    How to put change control into practice?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    140/158

    Although change control is very important process, it isnot easy to be practiced.You can do

    Design the change control process in project planningwith stakeholders.

    To be understood the process, it can be efficient tomake several chance to use this process forstakeholders as an exercise.

    5.1.4 Control Schedule

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    141/158

    Monitor the status of the project to update projectprogress and managing changes to the schedulebaseline.Project manager compare project schedule with workperformance information.

    It is very important to check the real performance. (Notto just believe the report.

    5.1.5 Cost control

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    142/158

    Monitor the status of the project to update the project

    budget and managing changes to the cost baseline.PM will use the inputs as follows;

    Project funding requirementsWork performance information

    5.1.6 Using Earned Value (1)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    143/158

    BAC Budget at Completion

    ReportDay

    PV Planned Value

    AC Actual Cost)

    EV Earned Value

    SV

    Schedule Valiance

    CV Cost Valiance

    VAC Variance atCompletion

    EAC Estimate at Completion (= AC + ETC = BAC / CPI)

    ETC Estima te to Completion

    Using Earned Value (2)

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    144/158

    PV Planned Value

    EV Earned Value

    AC Actual Cost

    SV Schedule Variance EV-PV

    SPI Schedule Performance Index EV/PV

    CV Cost Variance EV-AC

    CPI Cost Performance Index EV/AC

    BAC Budget at Completion

    EAC Estimate at Completion

    ETC Estimate to Complete EAC-AC

    VAC Variance at Completion BAC-EAC

    5.1.7 How to report your performance?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    145/158

    Now, you write a design of new system.

    The size of design paper is 100 pages and you havewritten 80 pages until now.How do you report about your performance using %?

    5.2 Manage Stakeholder Expectations5.2.1 Basic tools

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    146/158

    It is necessary to communicate and work with

    stakeholders to meet their needs.

    In stakeholder management, the project managerleads communications using below;

    Stakeholder registerStakeholder Management StrategyIssue LogChange Log

    5.2.2 Using Issue Log to manage problems

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    147/158

    In project, a lot of problems occur.

    To manage all, making issue log is effective way tomanage problems.Keep issue log in every meeting.Issue log is a reins for project manager to manage wellmany problems.

    Issue Log

    (1) Trouble in module A (date - name)

    (2) Claim from customer about supportsystem (date name)etc..

    5.3 Monitor and control risks

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    148/158

    Lose

    Reduce

    Expand Risks

    Change

    NewRisk

    Risk

    RiskRisk

    Risk

    Identify Risks

    Risk Analysis

    Plan RiskResponses

    Perform RiskPlan

    5.4 Administer Procurements

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    149/158

    Buyer

    Seller

    Monitor and Control Procurements thorough the project

    CloseContract ProjectManagement

    Review

    Report

    Case

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    150/158

    Inspection and Audits are effective way toadminister procurement. But in some case,you may have some trouble as follows;

    In middle phase of project, buyer request tomake an audit to check the schedule, sellerdenied it because of fixed price contract.

    How can you make an audit in such case?

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    151/158

    Project Closing

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    152/158

    6.1.2 Close Procurements

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    153/158

    The process of finalizing all activities across all of the

    Project Management Process Groups to formallycomplete the project or phase.

    ProjectManagement

    Plan

    CloseProject

    Organizational processassets updates

    CloseProcurements

    Closing CheckList / Closure

    Guidelines

    AcceptedDeliverables Deliverables

    6.2 Assess the project

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    154/158

    Make project final report for your organization.

    Final report should be the document for lesson learned.Good report point out the problems in process which areneeded to be resolved for next other project.

    Many stakeholders should be involved to write the reportincluding PM, PMO, Sales manager etc.

    Final report includes assessment of each processes

    and their actual performance.

    Sample Form of Project Final Report

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    155/158

    6.3 Give the feedback to project members

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    156/158

    One of the effective way to improve the motivation of

    project members for next project is giving feedback tothem at the end of the project.

    Feedback need to include some point as follows;

    Appreciation of his/her contributionHis/her strong pointHis/her weak point which can be improved in future

    Having celebration party with your stakeholders!

    Conclusion

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    157/158

    Although project management gives you systematic

    set of knowledge and skills, the application of PMBOKdoes not guarantee the project success. Also, the goal of project is not the application ofPMBOK but to get the result.

    So, you need to choose the appropriate processesfrom PMBOK which should be applied to your project.To do so correctly, you have to understand the reasonwhy each management process is needed.

    To do so smoothly, it is also good to use managementtemplates.

  • 8/11/2019 2010_SummerCourse_PM for Embedded Systems

    158/158

    ~ Thank you so much foryour participation~

    Good luck!