Ingredients for a Successful Project (Part 2)
In Part I of Ingredients for a Successful Project, we visited such areas as accepting chaos, work authorization signings, splitting scope, picking your team and requesting any prequel history that my exist on the project. All of which are great methods of getting a technology project started. In Part II, we'll visit areas that will help a technology project manager keep a project on track toward the finish line!
Weekly Meetings
Let's start light…weekly meetings are probably something you already do with your team. However, if you're the TPM and you have a fellow business manager or business project manager who's helping you manage the project, keep your technology team meetings separate from your meetings with the business partner.
I've seen many developers clamp up in a meeting when they know the business partner is amongst the crowd. Your technology team needs to know they can freely speak their mind to the one they must confide in--that someone being the TPM. If the business asks/requests to be included in the meetings, be sure to let them know they are not to step on anyone's toes in the meeting and that you are the IT lead. And let your technology team know beforehand that the business partner is coming, so that they are equally prepared.
Manage by Issues
It's a good practice to manage the risks before they turn into full-
Please log in or sign up below to read the rest of the article.
|
"It's kind of fun to do the impossible." - Walt Disney |




