Stakeholder Management

Stakeholder Management

  1. Identifying stakeholders by their weight (investment/impact/contribution)
  2. Understanding/analyzing stakeholders
  3. Identify stakeholders needs / responsibilities
  4. Defining stakeholders responsibilities / commitments
  5. Defining communication protocols/strategies
  6. Defining timelines, check points
  7. Review / Follow up to closure

 

Challenges:

  1. Power game / Ego problems
  2. Hidden motives/agenda of people
  3. Politics pollution
  4. Not adhering to commitments / protocols / boundaries / responsibilities

 

Good practices:

  1. Respect each person and understand them with respect to MBTI (Myers Briggs Type Indicator)
  2. Understand business needs
  3. Explain limitations/scope of roles and responsibilities
  4. Inform your peers and superiors that you are not competitor in job to minimize jealousy
  5. Communication and its timing is important
  6. Communicate clearly through email, which may help down the line.
  7. Know your limitations/scope/boundary and stay within it.
  8. Influence / motivate / encourage across the board
  9. Build relationships and accept the differences
  10. Build Trust and Credibility

 

Few words to think of

Expectation Management, conflict resolution, stress management, risk identification/mitigation, Contingency Plan, Resistance to change, Nepotism, Biased people, Corrupted minds, Communication styles, Brand Building, Negotiation, Damage Control, Listening Skills,

 

Dynamics of Stakeholder Management is different based on situation type. Few examples:

  1. Developing a product from scratch
  2. Doing volunteer project
  3. Family get together

 

Some of the bad things and it’s remedies:

  1. Not utilizing resource intentionally to side them in future: Be prepared to quit
  2. Not giving credit for any good and appreciating all others: Accept it and move on
  3. Showing ego and power in all possible places: Pray for them

 

Don’t do following under any circumstance:

  1. Never shout/bad mouthing or loose temper in meetings
  2. Never send negative emails to any. If there are issues, log defects in respective system
  3. Never feel jealousy with your peers
  4. Be positive and never lose your hope
  5. Don’t lick shoes

 

If you are successful in Stakeholder management, you are lucky. If not, try to minimize the damage. Worst case be ready to quit with dignity.

 

References:

Managing Stakeholders in Software Development Projects
by John McManus
Taylor and Francis © 2004 (196 pages)
ISBN:9780750664554

Managing Project Stakeholders: Building a Foundation to Achieve Project Goals Hardcover – April 22, 2013
by Tres Roeder (Author)

Mind Tools, essential skills for an excellent career
by Mind Tools Limited (Publisher), James Manktelow (Founder of Mind Tools)
http://www.louisediamond.com/cooperation/MindToolsEbook.pdf
https://www.mindtools.com

Stakeholder Communications Worksheet (Read above chapter and do this exercise)
https://www.mindtools.com/pages/article/newPPM_08.htm

———————————-*

Types of followers:

We need to see what type of followers your supervisor expects…..this helps to reduce conflicts

https://en.wikipedia.org/wiki/Followership

 

Kelley has identified 5 follower types

 

Sheep
“Yes” People
Pragmatics
Alienated
Star Followers
———————————-*

JIRA – Project Metrics for given story id’s

Defects
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (bug,Correction)
Defects Closed
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (bug,Correction) AND STATUS IN (RESOLVED, CLOSED)
Defects Not Closed
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (bug,Correction) AND STATUS not in (RESOLVED, CLOSED)
Stories
JQL: project = proj1 and key in ( proj-1234, proj-1235)
Story Closed
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (story) AND STATUS in (RESOLVED, CLOSED)
Story Not Closed
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (story) AND STATUS not in (RESOLVED, CLOSED)
Sub Task Closed
JQL: project = proj1  and  issuetype in subtaskIssueTypes() and parent in ( proj-1234, proj-1235) and status in (resolved, closed)
Sub Task Not Closed
JQL: project = proj1 and issuetype in subtaskIssueTypes() and parent in ( proj-1234, proj-1235) and status not in (resolved, closed)

How to build new project from scratch?

Problem Statement: How to build new project from scratch?

Step 1: Get all functional / Non-Functional Requirements.

Step 2: Identify components, communication flows, Users, …etc

Step 3: Prepare number of total requirements, assign numbers and do estimations

This helps to plan for budget, resources, infrastructure, ….etc

Step 4: Define the road map and identify phases to deliver it.

Step 5: Identify Risks and prepare risk management plan.

-o-
This is applicable for both software / non-software projects.

References:

http://www.successfulprojects.com

Road Map Planning: http://www.onedesk.com

Requirements Management: http://products.optimizory.com/rmsis