- Identifying stakeholders by their weight (investment/impact/contribution)
- Understanding/analyzing stakeholders
- Identify stakeholders needs / responsibilities
- Defining stakeholders responsibilities / commitments
- Defining communication protocols/strategies
- Defining timelines, check points
- Review / Follow up to closure
- Power game / Ego problems
- Hidden motives/agenda of people
- Politics pollution
- Not adhering to commitments / protocols / boundaries / responsibilities
- Respect each person and understand them with respect to MBTI (Myers Briggs Type Indicator)
- Understand business needs
- Explain limitations/scope of roles and responsibilities
- Inform your peers and superiors that you are not competitor in job to minimize jealousy
- Communication and its timing is important
- Communicate clearly through email, which may help down the line.
- Know your limitations/scope/boundary and stay within it.
- Influence / motivate / encourage across the board
- Build relationships and accept the differences
- 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:
- Developing a product from scratch
- Doing volunteer project
- Family get together
Some of the bad things and it’s remedies:
- Not utilizing resource intentionally to side them in future: Be prepared to quit
- Not giving credit for any good and appreciating all others: Accept it and move on
- Showing ego and power in all possible places: Pray for them
Don’t do following under any circumstance:
- Never shout/bad mouthing or loose temper in meetings
- Never send negative emails to any. If there are issues, log defects in respective system
- Never feel jealousy with your peers
- Be positive and never lose your hope
- 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.
Managing Stakeholders in Software Development Projects
by John McManus
Taylor and Francis © 2004 (196 pages)
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)
Stakeholder Communications Worksheet (Read above chapter and do this exercise)
Types of followers:
We need to see what type of followers your supervisor expects…..this helps to reduce conflicts
Kelley has identified 5 follower types
This is one simple/minimalist work flow.
JQL: project = proj1 and key in ( proj-1234, proj-1235) and type in (bug,Correction)
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)
JQL: project = proj1 and key in ( proj-1234, proj-1235)
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)
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.
This is applicable for both software / non-software projects.
Road Map Planning: http://www.onedesk.com
Requirements Management: http://products.optimizory.com/rmsis