15 Ground Rules for Project Team Management

March 9, 2010

People with diverse professional experiences and background have totally unique perspective on any issue.  When a new team is assembled for any project, its vital for the success of that project that all team member are aware of  the ground-rules for the project; similar to any sport.  You may have to read it to team and give a copy for reference.

Here is an example list that I have used for a project to keep team aligned.    Such ground-rules certainly eliminate unnecessary confusion and your business customer and team members like it defined beforehand.  Make sure, you also follow it and implement it.

  1. Project manager is the primary contact for any project related communication.
  2. All team members maintain their contact info on the team contact list with contact preference.
  3. All members attend required meetings and conference calls; if unable to attend, meeting organizer to be notified.  If key contributor is unable to attend, request to reschedule the meeting.
  4. Any planned day off or vacation must be communicated in advance to project manager so that project plan can be updated and impact to work, if any, can be analyzed.
  5. All project team members have access to project plan and  project logs (in a standard document format) and are aware of the assigned tasks and due dates.
  6. All team members are to be consulted about the reasonableness of the plan prior to management approval.
  7. All team members are required to validate their assignments and time allocated prior to the plan is baselined.
  8. All project team members have the responsibility to proactively notify the project manager about tasks, duration or dependencies they believe are missing (or any other needed changes to the plan) and confront issues directly and promptly.
  9. Project team members have the responsibility to notify any potential difficulties in meeting the schedule for any assigned tasks as soon as it is known by the team member.
  10. Each project team member is responsible for ensuring anticipated workload conflicts with other assignments are brought to the attention of the project manager.  Team members should ask for help if feeling “stuck” or falling behind the schedule instead of waiting for miracle.
  11. All team members are responsible to own, follow-up and provide updates on the assigned task (including but not limited to any identified risks, issues, changes, approvals, clarification from customer).  If any delay is observed, escalate to project manager.
  12. All  meeting minutes, key decisions, assumptions and business rules must be documented and all action items must be followed up and assigned to a resource with expected completion date. These items are usually mentioned in casual conversation.
  13. All project team members understand the scope of work.  Any work performed must be in the project plan and is in the project scope.  Anything that is absolutely needed but not part of the project plan, must be brought into project manager’s attention.
  14. All project team members confront issues directly and promptly.
  15. Only project manager submits all final deliverables to business customer for sign-off or approval.

What are other key things that you have found useful and we can add to this list?

Thank you for your visit and have a great day!


11 Principles of Leadership

August 20, 2009

 I came across 11 leadership principles of Marine Corps in Guide Book for Marines on the Internet and here is my interpretation of 11 principles.  I am interested in hearing from Marines about their leadership experience. 

  1. Take responsibility – we need to seek and take responsibilities if we need to grow; never shy away, whatever seems challenging will help you expand your perspective.
  2. Know yourself – reflect upon your strengths and weaknesses; seek improvement and understand that you can achieve only those goals that you set.
  3. Set an example– conduct your business in a professional manner; do not loose temper – small minds are bothered by small problems; not only work in your job but also work on your job as well.  Be a brand that people want to associate with.
  4. Develop your subordinates– consider this as part of your job; learn to delegate; as Zig Ziglar said “You can have everything in life that you want if you will just help enough other people get what they want“; give them opportunities to learn & grow;  guide them if they fit somewhere else.
  5. Be available – in every respect; be available to listen to problems and challenges people are facing; to motivate, to lead and to show right direction; to hear criticism; to take decisions and to act on time.
  6. Look after the welfare of your employees – the way you want your boss to look after your welfare; develop emotional intelligence; connect with people and find out what motivates them; do something that touches their lives; help them when they are in need.  Arrogance and ignorance will not take you to the top or won’t keep you there for long.
  7. Keep everyone well informed  – right communication is the key; make sure that the tasks are understood, supervised and accomplished on time and tell why you need all this done; do no assume –  aks and tell.
  8. Set goals that are achievable – always set the goals – people need to know what they are expected to deliver and by when; let people figure out how;  goals should motivate teams to act; measure the results and reward people.
  9. Make sound and timely decisions– that are aligned with the core principles of your organization and with your job descriptions; there will always be more than one right answer – choose the one that benefits the most and not only you; take decisions like a servant leader.
  10. Know your job – be technically and tactically proficient in your job; know your people; know the processes and challenges; know how can you add value to the organization or your department.
  11. Build teamwork– not all people can perform equally but they should complement each other while working towards a common goal; promote team work and diversity; shield your team from external pressure; be flexible with team.

“Leadership is intangible, hard to measure, and difficult to describe. It’s quality would seem to stem from many factors. But certainly they must include a measure of inherent ability to control and direct, self-confidence based on expert knowledge, initiative, loyalty, pride and sense of responsibility. Inherent ability cannot be instilled, but that which is latent or dormant can be developed. Other ingredients can be acquired. They are not easily learned. But leaders can be and are made.” – General C. B. Cates, 19th Commandant of the Marine Corps

Thanks for reading and welcome your input.  Have a great day.


Changepoint and PPM

June 5, 2009

Last week I completed Compuware Changepoint training. I had read earlier that Changepoint is in Gartner’s Magic Quadrant (leaders) for PPM tools.

Changepoint is a web based tool for project and portfolio management.  The tool enables leadership make right decisions based on dynamic metrics of various initiatives and what value these initiatives add; and realignment of IT efforts with business strategy and vision.  Tool is very intuitive and scalable. 

In Project and Portfolio management, complexity is the key factor that makes changes difficult and time consuming. Just imagine multiple projects going on in  your organization with resources scattered around the teams (or Globe) and you are tracking the progress and reporting the metrics to the upper management.  Management wants to see  report on  status of all the projects underway, return on investment for each project, supply and demand, resource utilization, change management, issues and risks to the projects, etc. to make informed decision on project priorities, strategic planning and funding.

Changepoint makes all the aspect of program management easier by effectively managing your projects and applications, resources and client relationships.  You can find out more at Compuware website.

Disclaimer – I am a Compuware employee and opinions expressed here are my own.


Project Management – Useful Links

April 8, 2009

We learn a lot from the Internet these days and rely on up-to-date information.  Personally, I’ve learned a lot from my fellow bloggers and other websites on Project Management to stay ahead of the curve. 

There are many other on-line resources but  I would like to share following list of blogs/websites that I frequently visit and would like to thank for their time and energy for sharing knowledge and doing the great service to on-line community.  Thank you and keep up the good job!

  1. http://www.betterprojects.net
  2. http://www.pmhut.com
  3.  http://www.thepmpodcast.com  
  4. http://herdingcats.typepad.com
  5. http://www.ravensbrain.com
  6. http://pmcrunch.com
  7. http://www.allpm.com
  8. http://www.amakar.com
  9.  http://leadinganswers.typepad.com

I hope you will also bookmark these sites and learn about the profession. 

Thanks for visiting and have a great day!


Capture Planning Assumptions

February 23, 2009

Your boss approaches you and tells that workplan is very good but customer wants to know how can we deliver the project sooner than promised?  Now you have to come up with a new workplan or make some adjustments based on new findings.  You put your thoughts together and go on to make changes/update and deliver the final document with required changes. 

And then your boss asks, why this task is due this particular day and why are we taking this long to complete, etc., etc…

You might have answers for most of the questions your boss has asked but it is of prime importance that you document all the assumptions you made while planning, does not matter how small or evident those assumptions are.

I would capture following –

  • why are you making these changes or what is the objective and if these objectives are aligned with customer expectations;
  • what are high-level or global assumptions for the plan being put in place (standardized assumptions);
  • why making change to time/scope/cost;
  • what are risks that can derail the work;
  • what are the opportunities that you are counting on;
  • who are the critical resources you have based your work on;
  • what exceptions from standard process did you make;
  • what compromises are built into the plan;
  • what is the impact on existing process (if any);
  • for budget tail of it : dollars spent per month; and
  • what are the key milestones.

I hope these are the basic questions that we should be able to answer from a Project Management perspective when talking about assumptions.  Let me know what your thoughts are and what else could be added to the list?

Thanks for reading it, appreaciate your feedback.


Choosing Team Lead

January 11, 2009

“People acting together as a group can accomplish things that no individual acting alone could ever hope  to bring about.” – FD Roosevelt

Each team members has unique work style, personal goals, skills, background and experience.  Each team member’s unique qualities and different attributes make a team complex unit where conflict, confusion, criticism will grow and finally bring the project to failure  if team is not led the proper way. 

In many I.T. projects,  Project Manager (PM) has a team leader who assists him or her in coordination of work, driving the team effort, listening and resolving team issues, guiding in making the appropriate tactical decisions, and above all providing expert advice on subject matter, among others.  Synergy and cooperation among team members are the key things for success of the project and for that,  a good team lead should be in place.  If you got a weak team leader, team will not perform and you will be spending all of energy in team issue management.  As a PM, you need to understand that your team leader should –

  1. understand the whole project along with project objectives and goals;
  2. be expert of the overall process who can guide team members;
  3. be able to handle pressure and conflict situations;
  4. understands the team dynamics and works to promote productive working conditions;
  5.  be a good team player and can get status of work from team members;
  6. be capable of resolving minor issues without your involvement;
  7. be able to negotiate and communicate with technical as well non-technical people involved;
  8. be proactive with qualities of a mentor and a coach and
  9. able to provide realistic and accurate feedback on time.

Hope this helps in making you decide whom to choose to lead your team.  Let me know what else can be added to the list.  Thanks for reading and have a good day.


Scheduling & Three Types of Tasks : MS Project

October 14, 2008

If you are new Project Manager or new to using MS Project,  when putting workplan together one of the question you may ask is – what type of task should I choose?

MS Project has 3 options –

  1. Fixed Duration;
  2. Fixed Units;
  3. Fixed Work. 

The choice will decide how MS Project schedules the work, in other words, which one of three remains fixed and other two change.  To make things easier to remember, Duration is in days, Work is in hours and Units are resources.  And formula to keep in mind is ‘wud’ i.e.   w(ork) = u(nit) * d(uration).

Summary table – Left green column is task type in MS Project; top red column is what we change; blue colums are rescheduled by MS project.

 

Change Duration

Change Unit

Change Work

Fixed Duration

 

Reschedules Work

Reschedules Units

Fixed Units

Reschedules Work

 

Reschedules Duration

Fixed Work

Reschedules Units

Reschedules Duration

 

Basically, 1day duration has 8 hrs of work with 1 unit or resource working 100%.

Read the rest of this entry »


%d bloggers like this: