Posts Tagged ‘Project Management’

PMP Certification – Project Manager Requirement?

Sunday, March 9th, 2008

A PMP certification is valuable, but not a requirement. Anyone that is a project manager should have a formal education in management. A PMP certification provides the education, but it is no “silver bullet” that you will be a great or even a good project manager.

If someone has a PMP certification and limited project experience, they can actually impede a project by putting process over results. Someone with limited project experience, regardless of their formal training, needs coaching and mentoring.

I would encourage any employer looking for a project manager to identified PMP certification as a desired requirement. If the project manager will be working unsupervised, an employer needs to hire a job candidate with a successful project management track record. I would encourage any project manager or aspiring project manager to get their PMP certification if they lack formal management experience.


Agile Methodologies, Sharing Backlog, Dispersed Project Teams

Saturday, March 1st, 2008

Agile methodologies definitely improve communications between developers, business leads, and stakeholders in terms of project success compared to “traditional” waterfall methods. This is true no matter where the coders are located or whether they are an outside vendor or not(I have not seen too many projects succeed that used the waterfall method).

Yes, I think it is key that you share your product backlog / prioritized task list with outside vendors that are working on your software product. That way they have more opportunity to anticipate your needs and see what work is probably coming their way in the coming weeks and months.


Gathering Functional Requirements For A Software Project

Saturday, March 1st, 2008

Every project is different, but in many cases it is best to gather and refine functional requirements in stages based on an initial charter document. For a large project the project lead should either identify or create some type of charter document that outlines the project’s purpose, scope, major deliverables / milestones, and a high-level cost estimate.

Instead of trying to identify all the functional requirements upfront, break the project into chunks. In build 1 define the functional requirements for a pilot project that keeps the users and stakeholders fully engaged in validating and refining the functional requirements. In each requirements and design phase as well as subsequent software builds, continue to work with stakeholders to update the overall functional requirements and review the charter document to assure project is on track.

The functional requirements should be definable, attainable, and decisive (i.e. link back to the project charter document and specific enough to guide software development). This allows the functional requirements to be traceable in that they can be measurable and be used to guide user acceptance testing and approving software for production.