How should a project manager plan communications for a project which has uncertain requirements?
A.
Include stakeholders in project meetings and reviews, use frequent checkpoints, and co-locate team members only.
B.
Invite customers to sprint planning and retrospective meetings, update the team quickly and on a daily basis, and use official communication channels.
C.
Adopt social networking to engage stakeholders, issue frequent and short messages, and use informal communication channels.
D.
Adopt a strong change control board process, establish focal points for main subjects, and promote formal and transparent communication.
I feel like B is the only one that works in todays environments and this sounds like an agile environment. A seems too old school with it being a must have to colocate people and seems a bit infrequent. Retrospectives in sprints are every 2 weeks and involve main stakeholders too. I am counting this one as right in my book haha
This approach focuses on establishing clear channels for managing changes through a robust change control process. Having focal points for key subjects aids in directing communications to address uncertainties effectively. Additionally, promoting formal and transparent communication helps in managing expectations and ensuring stakeholders are informed.
While options like involving stakeholders in project meetings (A), inviting customers to certain meetings (B), or using social networking for engagement (C) have their merits, in an environment with uncertain requirements, having a structured change control process and transparent formal communication channels is crucial to manage changes and keep stakeholders informed of developments and adjustments in the project.
For those of you who think that this seems too old school, I don't necessarily disagree, but this is good for types of consulting firms in large cities with agile methodologies and developers that can sit together and code together get real-time business analyst feedback etc. I have been a project coordinator on this exact type of project for my firm a few years back.
The key here is that in agile/adaptive environments, an emerging trend is to involve stakeholders in frequent checkpoints (we did progress meetings with our higher ups every two weeks at the end of every sprint before we got their sign off on the sprint deliverables, our product owner (project sponsor for agile) was in contact with higher ups frequently and he himself was in our daily scrums), etc.
A. makes sense. Just remember your basics for agile/adaptive and apply it to PM basics.
The "only" really made this question wonky for A...That makes it sound like we don't want to attempt to have the customer in the same location either. Or maybe there's a benefit to that? I'm not sure. I would assume if requirements are uncertain we would try our best to (reasonably) have the entire team and a customer rep in the room too to provide real time, tangible feedback.
"A" is correct for me because involves all stakeholders to the meetings and uses colocation. That ensures everyone is in line with the objectives and possible changes.
"D" uses Strong CCB, whis sounds like hard or difficult. Here we are expecting changes so we should facilitate them and reach a consensus, thats why A is better
My view is that it's just poorly written and should say "ensure all team members are co-located", essentially "only co-locate team members", i.e "don't allow multiple locations for team members"
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
andy20166
Highly Voted 6 months agoPradnyasachin
Most Recent 2 weeks, 1 day agoRocket20
5 months, 2 weeks ago[Removed]
5 months, 3 weeks agoszhang760
6 months, 1 week agoChymKuBoy
7 months agoCalvinthePM
9 months, 2 weeks agolimoncello
11 months, 2 weeks agoanfacer
1 year ago[Removed]
1 year agoMP_2022
1 year agoanfacer
1 year agopeacewishes
5 months, 2 weeks agotheplaceholder
4 months, 1 week agoMoonManBlue
3 years, 2 months ago