agile project management class three – communications project preview

Since there was no class this past week, I’m essentially going to pick up from APM class two‘s assignment and discuss what was done and how we got to where we are so far.

Assignment

The initial assignment was laid out in class as each team will explore a PMBOK Knowledge area (ie: Integration, Scope, Time, Cost, Quality, Human Resources, Communications, Risk & Procurement) in terms of how one would manage it using agile techniques.  Teams were eventually created and areas determined after some initial confusion, however, the more detailed requirements remain elusive.  My group is working on Communication.

The Group Dynamic & Strategy

So far, the strategy has been to focus on examples of how communication is used in Agile, although the correct deliverable still feels unclear even with a draft presentation complete.  I think my fellow group member is spending more time than I am on the project, but I’m hesitant to spend the extra time on something I’m not really sure of, in keeping with the spirit of the class itself.  It sounds like our group isn’t the only one struggling with the application of agile technique to the PMBOK knowledge area assignment either, so I’ll be curious to see how other groups finally tackle the problem.

After trading some initial notes and having a few quick meetings we were still unsure of the best direction to take with the assignment.  During the emails we would provide outlines and notes to one another based on research and concepting.  The chats we would refine the work in real time together.  After, we would review on our own, provide email feedback and then reconvene to make subsequent revisions together.  This is a similar way that my previous group operated and I find it effective both in time management and

The end result of our discussions was to select a situation where a project would be managed using agile, set out each of the five traditional process groups and map a specific agile technique’s communication assumptions over it.  The end result should show an overlay of traditional constraints and agile alternatives that can facilitate effective communications in the example environment.

Project notes

These are some of our initial project notes that came from a combination of email exchanges and short, real time chats and calls – it’s not really the finished assignment as we’d feel most comfortable handing it in.

Introduction:

Apply an agile methodology to the communication knowledge area by demonstrating use with a construction project example

Assumed Parameters:

  • Fixed Budget as approved by the city
  • Fixed timeline due to the seasons
  • Project must “Go Green”
  • Must have approval by community board and other stakeholders

Methodology Applied:   DSDM

Reasoning:

A number of “Green” concepts could be applied so determining the most cost and time effective ways to use them is important for project success.

DSDM provides communication feedback loops to address the range of potential concerns throughout the project’s lifecycle.  The risk is no single deliverable may be ensured when trying to balance the fixed requirements.

===

PM Process Agile Activity Agile Process Output Concern
Initiating Workshops

•Community consultations with city residents to gauge concerns

Meetings

•High level meetings with major stakeholders to address Feasibility study
-Stakeholder Identification:(- Funding agency, recipient- city, EPA rep, Architect, Civil Eng. QS, GC, Project team, Citizen Rep

 

-Pre-project/feasibility study- Decide : Musts,

Shoulds, coulds, and wont haves

 

-Feasibility Report

-Project outline–Acceptance of project implementation approach

-Risk log

-Public record of the meeting

-Citizen buy in of project due to bridge closures

-Can this project be done “green”?

-potential for cost overruns due to delays, materials for Green, etc.

-Potential time overrun due to Weather related delays
-Lack of high level requirements consensus
-Conflicting needs of stakeholders

===

PM Process Agile Activity Agile Process Output Concern
Planning
• Workshops with stakeholders for additional

Feasibility Study elements  and Business Study

• additional public forums to address community concerns

 

 

 

 

•-Business level and the information systems requirements identified.

 

 

-General Requirements List

-Architect produces final plan

– Itemized Budget

Project schedule

• public notices regarding  the project

-Updated Risk log specifically for high level requirements, budget  & weather related issues

-Stakeholder agreement may not occur
-Requirements may not be able to be met within fixed restrictions
-Requirements prioritization could cause conflicts
-Potential budget overruns
-Potential time overruns

===

PM Process Agile Activity Agile Process Output Concern
Monitoring  -Planning and development sessions with key stakeholders

– Oversight meeting & inspection such as with OSHA, EPA, etc.

-Community meetings for the public

 

 

-Functional Model Iteration

– Design & Build Iteration

– Key stakeholders provide revised inputs based on requirements through prototyping

– Model bridge to show methodologies that can be used

-Updated requirements list after rethinking and prioritization by stakeholders
-Public notices for progress
-Inspection certifications

-updated risk log

 

-Community feedback / non- acceptance
-Budget overruns – materials
-Time overruns – weather
-Requirement creep
-Prioritization conflicts
-Lack of high level requirements being met
-Failed inspections

===

PM Process Agile Activity Agile Process Output Concern
Control  Team meetings

 

Site visits

 

 

–Functional Model Iteration

– Design & Build Iteration

-Maintain Project on critical path & Progress Review

 

-specific Requirements List

-Architect produces final plan

– Itemized Budget

Project schedule

& Updated Risk log

 

– Resources availability

– Time overruns due to weather

-budget overruns

-Inability to make usable revisions to changing requirements
-Saftey & EPA sign offs

===

PM Process Agile Activity Agile Process Output Concern
Closing Testing/ Walk through

checking bridge before opening

 

Project Review

 

Final public meetings

 

Implementation Completed Bridge

Documentation handed over to user/city authority

-EPA sign off

– Safety inspector sign off

-citizen feed back

-All initial issues addressed
-Within budget

 

===

 

I’m not convinced our approach is correct, but we need to create something as a starting point.  Since this took me just over the allotted two week four hour budget to work on I am OK with using it as a foundation for the class to review and critique as an initial presentation.

 

 

Advertisements

About thedoormouse

I am I. That’s all that i am. my little mousehole in cyberspace of fiction, recipes, sacrasm, op-ed on music, sports, and other notations both grand and tiny: https://thedmouse.wordpress.com/about-thedmouse/
This entry was posted in business commentary, Opinion. Bookmark the permalink.

One Response to agile project management class three – communications project preview

  1. Pingback: agile project management class three – communications continued « doormouse’s declarations and personal attributions

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s