COMP3120_13_Comms_Management_2010v1

COMP3120_13_Comms_Management_2010v1 - MANAGING SOFTWARE...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
MANAGING SOFTWARE DEVELOPMENT COMP 3120 HUMAN RESOURCE MANAGEMENT Mark Grundy, Ian Hirst
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 2 Agenda " Why Communications Matter " Kinds of Communications " Concerns " Key Skills " PMBOK Processes Identify Stakeholders Plan Communications Distribute Information Manage Stakeholder Expectations Report Performance " What Can go Wrong " Conclusions
Background image of page 2
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 3 Why Communications Matter
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 4 Some Kinds of Project Communications Purposes: " Report – to be accountable " Inquire – to be informed " Inform – to help decisions " Explore – to understand " Predict – to anticipate " Advocate – to create change Modes: " Internal/External " Formal/Informal " Vertical/Horizontal " Official/Unofficial " Written/Oral " Verbal/Non-verbal
Background image of page 4
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 5 Communication Concerns " Stakeholder knowledge, understanding " Team knowledge, understanding " Stakeholder opinions, expectations " Stakeholder power/influence, decisions " Team behaviour " Stakeholder behaviour " Project, team reputation Timeliness, appropriateness, robustness of Visibility, activity, commitment, authority of project support
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 6 Key Communication Skills " Active Listening " Questioning " Educating " Fact-finding " Setting/managing expectations " Persuading/influencing " Negotiating " Resolving conflict " Summarising, identifying next steps
Background image of page 6
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 7 PMBOK Processes " Identify Stakeholders " Plan Communications " Distribute Information " Manage Stakeholder Expectations " Report Performance
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 8 PMBOK Process -- Identify Stakeholders " Inputs: Project Charter Procurement Documents Enterprise Environment Factors Organisational Process Assets " Stakeholder Analysis Expert Judgement " Outputs Stakeholder register Stakeholder management strategy
Background image of page 8
COMP3120 - Managing Software Development Mark Grundy, Ian Hirst 9 Identify Stakeholders Stakeholder Analysis 1.
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/12/2010 for the course CSIT COMP3120 taught by Professor Markgrundy during the Three '10 term at Australian National University.

Page1 / 25

COMP3120_13_Comms_Management_2010v1 - MANAGING SOFTWARE...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online