We Must Succeed - Project Management | Development | Technology

Have a question? What are your thoughts, responses, experiences?

2005-11-20T19:31:00.000-08:00

?Ask the Facilitator?
Get your project/program management questions answered. Don't allow another failed project due to lack of knowing how to do the job right. Ask the facilitator, click here...

A Career of Significant Project Management Lessons Learned

2005-11-20T19:12:00.000-08:00

It's about Management Control and Quality
The following is a list of 29 project management lessons learned that I have identified and documented....

Click here for Project Management Lessons Learned

2005-11-04T22:14:00.000-08:00

Program and Project Management. Is There A Difference?
Yes There Is...

There is a difference but some professionals in the IT industry seem to think program management is just managing multiple projects. Program and Project Managers may or may not be certified.

Program Management
Program management is the management of multiple related projects, a system or systems, not just multiple projects. A Program Manager has project managers, technical leads, and/or project leads reporting to him/her. A Program Manager (PM) provides technical and business leadership as required. Program Managers are involved up front in system/product development, with sales, customer relations, contract development and negotiations, etc. The Program manager is required to be familiar with different technologies, methodologies and processes for different practices (e.g., software/application, networks/infrastructure) and experience with the System/Software Development Life Cycle. Where some project managers may not control their budgets (but should) program managers have financial and budget responsibility. The PM has communication, team building, business management, and subcontract/vendor management skills. A program manager must be familiar with various standards related to technology in various industries.

Project Management
Project Management is normally about managing a set or related project tasks/activities for a single product. A Project Manager (PM) may be certified and have the required background or experience. The PM is capable of managing a variety of technology projects but usually in his/her particular expertise or discipline (e.g., application development). PM's are directly responsible for the product(s) and deliverables resulting from successfully completed projects. A PM understands the technologies, methodologies, tools, and basic best practice processes applied to a particular project, and should posses planning and communication skills.

Download The Project Management
Best Practices Report Today..

Project Management Best Practice Processes

2005-10-07T19:05:00.000-07:00

Full report will be completed soon.

Where is our success? Although there have been improvements, over 60% of projects/programsfailed and many were canceled in 2003 (ref:The Standish Report CHAOS)! Our goalfor 2004 and beyond is to contribute to a 60% and better, project/program success rate! STOP THE MADNESS-MANAGE AND CONTROL PROJECTS SUCCESSFULLY!

The following is a brief outline of project management best practice processes. The COMPLETE detailed report is currently being written. Click Here and Sign up to be notified upon completion of the full report (your information will not be shared with any other parties). A full detailed lessons learned report is also in development for future release. The comprehensive Project/Program & Configuration Management Guide/Reference is available now
in softcover and electronic versions. Order Today!

Program/Project Management (and Business Management) (Integration)
- Use of Experience and Knowledge (Integration)
- Planning and Scheduling/WBS (Scope/Time/Cost)
- Communication Planning (Communication)
- Status & Earned Value Reporting (Communication)
- Performance (metrics) Reporting (Communication)
- Risks Identification and Management (Risks)
- Project Repository/DB (Communication/Lessons Learned/Knowledge
  Transfer)
- Change Management (Integration)
- Subcontractor/Vendor Control (Procurement)
- Team Building (Human Resource)

Development Process (Integration/Solution/Scope)
- Selection of the appropriate model/technique (e.g., Interative, Waterfall,
  Spiral, Evolutionary, Object Oriented, Structured)
- Selection of the appropriate implementation methodology (e.g., MSF,
  RUP, GXP, DOD-STD 2167 and other standards)
- Selection, if required, to use Rapid Development
- Rapid Application Development/Joint Application Development (RAD/JAD)
- Prototypes and Mockups
- Interviews and Facilitated Sessions
- Collaboration
- Selection of technical and project reviews
- Selection of development and support tools and applications

Configuration Management (Integration/Scope/Control) (described in the book, "Software and Firmware Configuration Management, " subtitled "Management
Control and Quality".)
- Configuration Identification
- Configuration Control - Software/Application, Firmware (Embedded Software, and Systems)
- Configuration Status Accounting
- Configuration Audits

Quality Assurance (Integration/Quality/Control)
- Verification
- Validation
- Testing

Some of the organizations that support these practices and certifications for their professional knowledge recognized in many industries are: Project Management Institute (PMI) , American Management Association (AMA), Software Engineering Institute (SEI), Electronic Industries Association (EIA), Institute of Electrical and Electronic Engineers (IEEE), International Organization for Standardization(ISO), and the Department of Defense (DOD).

Use this article on your website or in your newsletter...click here for the article and syndication guidelines