Monday, September 06, 2010

Enter Title

Minimize

I am launching this Project Management Wiki to give a PMs a place to hang out, share information, improve their process and for people who want to become project managers.  Since I am an IT and software development project manager by trade, this Wiki will revolve around IT.

  

Wiki

Minimize
Home
No Comments Yet

Advice to PM's everywhere.

1. Spend more time in the design stage.  The complaint I most often hear from coders is that the application they are being asked to code was not properly designed.  Some tell me there is little if no time spent in design.  Spending time in design and involving the development team in the design assures better applications, shorter phases after design, and happier developers.  Everyone wants to know their opinion is important, especially the team members doing the actual development of your project.  Slow down and design, involve your developers, produce a better more scalable product, and an increase ROI for your client.

2.  Listen.  This actually applies to #1, but expands of course to the clients and all the internal teams.  Sometimes we get so caught up in our own knowledge that we don't listen as closely to the actual users of the applications in which we oversee development.  The next time you’re talking to someone outside the development team and they say, "it bugs me when the cursor doesn't land in the field when I first go to that form", stop and note this comment.  It's the little things that make applications successful.

I find that these little comments actually lend themselves to better team practices.  In my example, it would be a good idea to coach the development staff to ALWAYS place the cursor where it should be when a user lands on a form.  These minor details make us better professionals and give us happier users.  It all starts with listening closely to the stakeholders.

3. Optimism. Everything is not broken. The files are on the server, right? Stop and work backwards, you can find the good. Developers and stakeholders respond better to positives. They will be more productive and have a better feeling about the overall progress of your project if you express optimism. So, the next time a stakeholder kicks you in the shin and says, this is wrong and that is wrong, thank them. “Thank you so much for taking your time to help us correct the application/project.” Try relaying these constructive criticisms in an optimistic posture back to the development team. “Wow, the good news is stakeholder X took some time to relay some problems they found in our project/application and the great news is we can fix them.” I personally never find things bad. Bad is good, so to speak. Bad is a chance to fix and be better.
 
Here is a great article I read recently about how to be an optimist.  Click Here

 Happy project management!

Dave



  Rating
Rate This Page: Poor Great   |  Rate Content |
Average rating:  4.4   
12345
Number of Ratings : 5
  Comments

 |  View Topic History  |
  
Copyright 2006-2009 Two Peas Consulting