Thursday, June 12, 2014

Handling Scope Creep


Scope creep is one of the biggest problems a project manager has to deal with.  The availability of new material can be a cause of scope creep or sometimes even new rules and regulations; the end result is that the scope expands and the project manager must determine how to proceed.  Often times, changes may seem small and that they won’t require more time or resources to accomplish but these can grow into larger changes and jeopardize the success of the project if not thoroughly reviewed and evaluated before approval (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).

One of the first projects I worked on as a new educator was an upgrade of our e-mail system from GroupWise 5 to GroupWise 5.5.  My role as the educator was to identify the most common current uses of the system and develop the training material, curriculum and provide instructor led classes so the staff would know how to use the system to perform their jobs when we went live.  Well into the project, someone determined that we should also introduce the Document Management feature which allowed shared file storage.  This certainly changed things drastically from a training perspective.  Staff already had existing knowledge of e-mail used in a corporate setting however shared files were pretty much unheard of at that point; the cloud did not exist.  The technicians also needed to build extra servers to accommodate additional files and network security needed to be introduced.  For several weeks, the team really tried to pull it off.  In the end though, there just weren’t enough resources on the project to accomplish the extra goals and objectives associated with document management.  We rolled back to the original project, now with a delayed timeline, and started implementing just the e-mail upgrade.  

Now that I have a bit more experience as a team member and as a project manager, I can
see that this could have been avoided if a change management procedure had been put in
place before any requests for change occurred.  When a project manager is faced with
making a decision, they may feel pressured to give a quick answer and not think thoroughly about all of the consequences (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).  A project manager should evaluate change requests closely so they can be analyzed so that impacts to the schedule, cost, or objectives can be clearly articulated and defended to the project sponsor for written approval (Greer, 2010).  By gathering and sharing all of the pertinent information, the stakeholders can choose if the change is worth the impacts it could cause. 


References

Greer, M. (2010). The project management minimalist: Just enough PM to rock your projects! (Laureate custom ed.). Baltimore: Laureate Education, Inc.

Portny, S. E., Mantel, S. J., Meredith, J. R., Shafer, S. M., Sutton, M. M., & Kramer, B. E. (2008). Project management: Planning, scheduling, and controlling projects. Hoboken, NJ: John Wiley & Sons, Inc.

Wednesday, June 4, 2014

Time and Cost Estimates for Instructional Design



As an Instructional designer and new project manager, I haven’t had much experience estimating costs associated with a project.  I have considered the students’ time (usually calculated using an average rate of pay for staff) but I never thought to weigh that against my time and other SMEs time to produce anything resembling ROI (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).  I often find myself feeling like there is way too much effort expended on some projects to get the desired result.  I would really like to pop some data into a spreadsheet, let it calculate and know if proceeding with a project is the right thing to do.

I was recently asked to convert a 2 ½ hour instructor led course on nursing documentation in to an asynchronous online course.  In the request, she stated she would be willing to do all the work however; I don’t think she understands the number of hours that will go into this project.  The search for cost estimators I found Big Dog & Little Dog’s Performance Juxtaposition website.  It’s a great Instructions Design site in general but the reason I got excited initially is the development time to instructional time ratios.  Based on their estimates, this course conversion will take approximately 550 hours before we can use it.  Considering we currently hold the class once a month, it will take us until the end of next year to even out the instructor hours we would save.  This is not a sound project, financially speaking.  Since the content is based on software that has quarterly changes, we will likely need to update it before we realize our payback as well.

After searching for more sites with estimators, I came across several others that were close to the 220 hour estimate.  One stood out at a whopping 490 hours for advanced eLearning design and development.  If I use this it would take us about 1225 hours, with an equivalent instructor time at a little over 4 years.  This would surly convince her that this is not a worthwhile use of our time but why the huge disparity?  The Dashe & Thompson Social Learning Blog goes on to explain why instructional designers shouldn’t simply plug a number into a spreadsheet to get a time estimate (like I wanted).  With very large, multi-chapter courses, development time will go down as you progress in the project.  For example, if you need to create 20 chapters the first one will most likely take the longest amount of time.  As you get a system going, you find efficiencies and by the last couple of chapters you spend very little time. 

These are both great sites that I plan to review in more detail; I wish I had found them soon as I think they would have been a great help through some of the other courses in this program.  Hopefully you can also benefit from them. 


References

Clark, D.R. (2010). Estimating Costs and Time in Instructional Design. Retrieved from http://www.nwlink.com/~donclark/hrd/costs.html, June 4, 2014.

Matajcek, J. (2010). Why eLearning Development Ratios Can be Hazardous to Your Career. Retrieved from http://www.dashe.com/blog/elearning/development-ratios-hazardous-career/, June 4, 2014.

Portny, S. E., Mantel, S. J., Meredith, J. R., Shafer, S. M., Sutton, M. M., & Kramer, B. E. (2008). Project management: Planning, scheduling, and controlling projects. Hoboken, NJ: John Wiley & Sons, Inc.

Tuesday, May 20, 2014

Effective Communication in Project Management



Effective Communicating is crucial to a project manager.  With any project, one task relies on others so a few missed deadlines can cause a project to be severely late.  Key stakeholders may not support a project if they are not given enough information.  Not listening effectively can mean that a critical component was not identified until later in a project causing re-work for the team.  Any of these issues can cause a project to fail.  Project managers must communicate well both orally and in writing to avoid such problems (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).


As I read the e-mail from Jane regarding the report Mark was supposed to complete, I interpreted that Mark was late with the report and that his lateness was holding Jane up from completing her work. The written communication was very professional and I felt a real sense of urgency in the tone of the e-mail.  According to Dr. Stolovitch, written communication should state a clear purpose, include possible solutions and specify the type of response (Laureate Education, n.d.).  Jane did include a possible solution by offering to
accept just the data if Mark was not ready to send the entire report however the message would have been more clear if she has stated when and how she needed to hear back from Mark.  The same message in a voicemail left me feeling less urgency however I still got the impression that Mark was late with his report.  The face-to-face conversation left me with no sense of importance whatsoever.  Mark could continue being late with his work and Jane would just keep on smiling about not getting her own work done (Laureate Education, n.d.). 


Since I began the exercise with the e-mail communication which had a more forceful tone, the voicemail and face-to-face communications both seemed to lack the urgency of Jane’s need for the data from Mark’s report.  I wonder if I had approached the task in reverse if I would feel the same way.  Maybe Mark was not late; this was never stated however I got this impression from the first modality and it stuck with me while I reviewed the others. It is possible that this skewed by view of the voicemail and face-to-face conversations.  Given that Jane is approaching a deadline and is worried about being late though, I have to believe that there is some urgency in the message and that the most effective message in this case was the e-mail message.  


Though it is important to document conversations regarding a project; especially one that is discussing deadlines, I think I would choose to have a face-to face conversations in this situation in order to get the commitment from Mark to deliver what I needed in time (Laureate Education, n. d.).  Of course this may be influenced some by what has worked with this stakeholder in the past, if there is a known history or pattern (Laureate Education, n.d.).  In most cases, holding the conversation face-to-face seems to soften the message which would be very helpful when discussing topics that are particularly controversial.  Tone and body language can help get the true meaning of a message across to the stakeholders. 



References

Laureate Education (Producer). (n.d.). Communicating with stakeholders [Video file]. Retrieved from https://class.waldenu.edu 

Laureate Education (Producer). (n.d.). Practitioner voices: Strategies for working with stakeholders [Video file]. Retrieved from https://class.waldenu.edu 

Laureate Education (Producer). (n.d.). Multimedia Program: "The Art of Effective Communication" Retrieved from http://mym.cdn.laureate-media.com/2dett4d/Walden/EDUC/6145/03/mm/aoc/index.html 

Portny, S. E., Mantel, S. J., Meredith, J. R., Shafer, S. M., Sutton, M. M., & Kramer, B. E. (2008). Project management: Planning, scheduling, and controlling projects. Hoboken, NJ: John Wiley & Sons, Inc.

Thursday, May 15, 2014

Lessons Learned from a First-Time Project Manager



Several months ago, I was enlisted to manage the redesign of our corporate orientation.  My team was tasked with creating an event that would enculturate staff to the corporation’s mission, vision, values and strategic initiatives and it needed to be relevant for all staff across the system.  The existing orientation was 13 hours long with 17 different presenters.  It had not been overhauled in about 10 years so the content was largely directed toward the employees based at the main hospital campus; we needed to start over and include the physician practices our fitness club.  Our team
consisted of six core team members who needed to attend most of were expected regularly attend all meetings and were responsible for most of the work as well as five extended team members who attended only the meetings they are needed for.  We officially close the project tomorrow and while we did accomplished the goals and objectives of the project and our metrics all met or exceeded expectations, there were stumbling blocks along the way that we could have avoided.  We use a standard, 3-question post mortem:

  • What went well? 
  • What could be improved?
  • What lessons have you shared?

These questions helped determine lessons learned however the phase-specific questions recommended by Greer (2010) would garner more specific responses and recommendations. 


The Beginning: Chartering

What could have been better?       

Two hours before my first meeting with the project team, the executive sponsor changed the primary objective of the project from reducing the hours of instruction to ensuring all the content was linked to the mission, vision, values and strategic plans.  Since the data collected from participants and organization leaders clearly showed the need to reduce the time spent in orientation, I was a little confused by the change.  As it turned out, the executive sponsor was simply using the project as a way to push her own agenda.  In retrospect, I should have postponed the kick-off and allowed time thoroughly re-evaluated the charter, metrics and timeline.  I had been waiting so long to get the project off the ground I just pushed ahead.  It wasn’t until a few weeks later that I realized how much this change affected the amount of work to be done and that I might not meet the deadline.  My own flexibility was nearly the downfall of my project.  If the charter included the right elements from the start, we wouldn’t have needed any changes (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008). 

What worked well?

With the new primary objective in place, I also needed to re-work the metrics that were to be our measure of success.  Setting measurable objectives that one can track and trend at the front-end of a project gives the team the requirement they are working towards and informs you of when you have achieved success.  Our metrics served as a guiding light whenever we would start to get a little off track or if there was even a hint of scope creep (Laureate Education, n.d.).

The Project Plan

What could have been better?

The Nursing Education Department delivers a unit specific orientation for new nurses so we included the organizer of this program as an extended team member to identify conflicts, overlaps, and deficits between the two programs as well as anticipate how the programs might need to change in order to work together.  As an extended team member, she was not required to attend the weekly meetings but did receive written updates and we had coffee a couple of times to talk about the progress of the team.  Unfortunately, at implementation, I found out she had not shared the information with her team so they were understandably confused and upset by the changes that impacted them.  At this stage of the project, having to smooth ruffled feathers and rework some of the processes added undo stress to the team and could have been avoided (Greer, 2010).  Looking back I recall having a verbal conversation about her role on the team and we spoke about communicating the changes back to her team.  In the future, I will consider using a work-order agreement and put tasks on our project plan specific to the expectation of communicating information back to the team (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008). 

The Executive Sponsor of my project was also one of the people that needed to re-write content for the revised program.  Though she set the goals and objectives for the project and even a few of the deadlines, she consistently did not meet the deadlines she agreed to.  Our first session was held Monday at 8 am and she finally provided her PowerPoint presentation at 6 am.  Looking back, I am not sure understood the time required to design effective learning (Murphy, 1994).  This presented a very difficult situation to deal with because as the executive sponsor she was supposed to help work through the barriers the team identified not create more of them.  In the future, I will attempt to identify the key points she wants input on and when we need her approval to move on well in advance. 

 What worked well?

The Gantt chart is a project manager’s best friend.  I don’t think I could have survived without this tool.  I used Visio to create a very large list of tasks; I then linked them and created dependencies.  Team members then estimated the number of days to complete the tasks they were assigned.  After all of the tasks have a person assigned and time-frames
filled in, you can see the end date of your project.  Having a written plan ensured we didn’t lose track of anything (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).  Every meeting the team would report their progress on tasks and it was so fulfilling to see the bars changing color and showing us our progress. 



Implementation

What could have been better?

Because the team champion and the executive sponsor had some time off, the memo announcing the changes did not get approved and sent to leaders until after the change had taken place.  Clearly this was not ideal but with so many moving parts to this project we could not roll back to the old way.  I have since been introduced to a communication planning tool that I think would have helped the team identify major points of communication in advance

 What worked well?

Because we identified a gap in the communication plan, we needed to implement interim measures to manage issues that came up (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008).  Since the change only affects a leader when they have a new employee starting work so we reached out to each hiring manager that had a person starting to personally explain the new process.  Even though some of the information we were sharing was new and even contrary to information they had recently received, the managers really appreciated the personal attention from the team and the opportunity to ask questions face to face.  We will be continuing with this practice until the organizational leadership gets more familiar with the steps in the process.


References

Greer, M. (2010). The project management minimalist: Just enough PM to rock your projects! (Laureate custom ed.). Baltimore: Laureate Education, Inc.
Laureate Education (Producer). (n.d.). Project management concerns: ‘Scope creep’ [Video file]. Retrieved from https://class.waldenu.edu 
Murphy, C. (1994). Utilizing project management techniques in the design of instructional materials. Performance & Instruction, 33(3), 9–11.
Portny, S. E., Mantel, S. J., Meredith, J. R., Shafer, S. M., Sutton, M. M., & Kramer, B. E. (2008). Project management: Planning, scheduling, and controlling projects. Hoboken, NJ: John Wiley & Sons, Inc.