This agile communication method is true for deadlines as well. Setting small, intermediary deadlines with clients and then being held responsible for meeting them – together – keeps the project rolling. With regular discussions, the blocking needs are identified early on in the project so that they can be handled with minimal overall impact. Often a vendor is looking for a client decision, but the clients can’t make that decision on the spot. At regular meetings, these details can be intelligently slid around so as to minimize the impact, and together discover what parts of the project can keep moving even while one part may be blocked. An updated timeline should always be an outcome of a meeting – one that all participants have had the chance to buy into.
Despite doing all of the above well, sometimes things just aren’t working for one or both parties to a software development project. In my experience, this will become evident during regular meetings, or when meetings start getting canceled often. Project meetings as a barometer of project health are a crude measure, but they may just provide the window needed to save a project, or to negotiate a wind-down on the best terms possible.
What are your project management meeting outcomes? Share your experiences in the comments below, or with me at @trackmymind on Twitter. Happy projects, y’all!
Director of Digital Marketing
RT @tmaund: How organizations are connecting their on-premises identities to Azure AD https://t.co/k22K6g1uA4
RT @msclouditpro: Time for Episode 40! – @ciphertxt and @benstegink go over some of the big @Office365 News for November 2017 - #Microsoft…