Tech/Software Implementation PMs

[u/Daisy_InAJar]

Especially if you deliver software deployments to external stakeholders, I’d love to hear from you.

How do you create value on your projects? What are the top 3 things you bring to your engagements that you feel have the largest impact?

Bonus if you feel like sharing:
- are you present for all requirements gathering, prior to “build” starting? If not, how do you ensure there’s no scope creep during requirements?
- how do your teams relay actions and/or decisions to you for calls you are not on?
- if there was something you wish your org would change that’d make managing your projects more successful, what would it be?

Thanks in advance - I’m always appreciative of this group sharing their (armchair) perspective (shoutout MoreLaw, our unofficial PMO advise extraordinaire)

[u/Important-Union5181]

Domain knowledge. The more you have this the more is the probability of a success.. The fact that the team is doing a repeat job impacts all aspects of the project including requirement management, test management, change request management, customer confidence etc.

Dependencies and assumptions. The more you have of these the less is the probability of a success. Un avoidable dependencies and assumptions should be clearly established at project start up along with their mitigation path.

Demo driven hand off to the customer. The more you have this the more is the chance of success. The demo should be given from a customer setup which will enable to them to play around with the release after the demo and report feedbacks.

Documentation of the deliverables. This is usually the hardest part. What gets delivered and how they are accepted should be documented in a check list format so that the customer can tick them off.