2009-01-08 January 2009 (PMBOK vs BABOK Part II)

Attendees - 14
--------------------
Christrine Cox - Stanfield Systems
Jack Ryder - Robbinsgloid
Don Crain
Connie Culbertson
Ron McClure - Self
Greg Kulak - HP
Patricial Userbach - self
Tom Carlos - Carlos Consulting
Debi Safranek
Kathi McCoey
Larry Mitchel
Nancy Nichols - Meta Vista Consulting
Collie Johsen
Carter Engelhart

Presenter: Errol Thomas of Pulic Sector Consulting.

Brief informal notes below. See also Errol's attached presentation

Enterprise Analysis - explore if a particular project should be done. BA involved at this stage. PM gets involved once the project is selected

PM focuses on planning the Project.

BA focuses on planning the Project

Both align themselves to the Project Sponsor.

BA and PM work together with the same groups of subject matter experts, functional managers, IT and executive staff. Develop the relashonships early and maintain them along the way.

PM is accountable for the final delivery of the product of the project.

BA verifies that the solution meets requirements. Signoff of the design document.
User acceptance testing is needed to achieve signoff.

Both PM and BA identify stakeholders. If a change in the product or have authority over the product they are #1 priority people. If I'm involved in the product but have no authority that would be #2 and #3 would be the PM and everyone else.

KSAB - Knowledge, Skills, Abilities and Behavior.

BA - Patient with users (drawing out requirements from SME's)

PM - Typically shows inpatience.

BA and PM are sensitive to the organization (e.g. Am I working with Morning and Afternoon people.

Glossary of terms that apply to the project and requirements should be defined so that everyone understands.

Group Discussion.
----------------------

What do we do as Project Manager - Look for the Business Analyst first. We need a trained Business Analysts on each.