Thursday, June 7, 2012

Man, That's Creepy


Some Background

     In early December of 2011, an email went out to every middle school teacher in the district.  The email was a search for middle school science teachers who would be willing to serve on a district wide committee that would be responsible for choosing the new middle school science resources for the district.  The district secondary learning specialist, the math intervention-learning specialist, and the district school technology specialist would lead the committee.  The committee would be comprised of   two science teachers from each middle school. Ideally, each school would have enough teachers that an application process would take place and teachers would be selected from the application pool.  As it would turn out, only one teacher from my school volunteered to be on the committee, which still left one more person that would need to volunteer from my department.  When I proposed this to my department at our monthly meeting, there was no interest.  So being the department chair, I went ahead and volunteered to be the second representative.

Some More Background

     The expectation for teachers who are part of this committee would be several days off the floor in order to take part in committee activities.  These activities would include defining criteria of the resources to review, narrowing the resource publishers to no more than four by the end of December, review of resources and publisher presentations, and a recommendation of the chosen resource to the school board by the first week of April 2012. 

Creeping up.

     This project experienced several different forms of scope creep.  The first began after the second meeting in Mid December.  At the end of the second meeting, the teachers voted and approved a group of four publishers who would present their resources in mid January.  The scope creep occurred when our project manager informed us that two other publishers, who were not part of the original review, would be added to the presentations for review in mid January.  Because of the extra publishers, a second day of review and presentations would be necessary in order to gather needed information. 

     The second instance of scope creep occurred at the end of the second day of presentations and review.  At this time, the committee narrowed the choice down to two different publishers.  One that was technology based, and the other that took a more project based approach to science instruction.  At this time, the committee was asked by the committee leaders to pilot one group of resources or the other in order to gather data that could then be shared with the group in a meeting that would take place in early February of 2012.  This would add a considerable workload to the members of the committee, as they would need to incorporate these resources into lessons that had already been planned and designed.

     A third occurrence of scope creep took place when the committee met in February.  Despite the intention to pilot the resources, some teachers did not receive the resources from one of the publishers in a timely fashion.  As a result, a few of the committee members could not provide the feedback that was requested at the January meeting.  To go along with this, the committee leaders were informed by the head of the district learning services that the committee would need to do a full alignment comparison of each resource to the new state standards.  In the end, this alignment would mean yet another day off the floor, and would add yet more time to our timeline.  Already it was becoming obvious that we would not be able to meet the original district deadline of early April.

     Two final instances of scope creep would occur once we were finally able to complete the standards alignment comparison, and make the recommendation.  The first came once the recommendation had been made by the committee.  It was at this time we were informed we would need to take a much larger role in the presentation of our recommendation to the school board.  Originally, we were informed that all we would need to do was make our recommendation.  The school board revised this, because on the initial presentation by the committee leaders, the board decided they wanted to be able to question committee members and gain a greater understanding of our thinking behind the recommendation.  The second instance would come when our presentation was bumped from the meeting in early May to the end of May due to other district business.  In the end, our recommendation was approved over a month later than originally projected. 

Hindsight is 20/20

     From my perspective, I am not sure most of the scope creep could have been avoided.  I really feel like the project manager did an above average job of monitoring the project (Portny, Mantel, Meredith, Shafer, & Sutton, with Kramer, 2008) and trying to stay ahead the inevitable scope creep.  One might point to the addition of the two publishers as avoidable scope creep, however it would turn out the recommendation by the committee would turn out to be one of the resources that was added late in the review process.  As far as the other scope creep that occurred, those were instances that came from outside influences such as district superiors, school board requests, and the state department of education.  In the end, one change that could have been made in order to reach the original deadline would have been to start the process sooner.  The original delivery date of early April was going to be tight even without any type of scope creep.  Starting the process sooner seems like a logical, but it is unknown whether the leadership team was available to begin the project process sooner.

References

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

5 comments:

  1. Genise-

    While I was reading your post about scope creep in your project, I kept thinking- maybe scope creep isn't always bad. As you stated some of the information that was added, was helpful. And the additional choices that were added late, actually gave you a winner. So is scope creep always bad? In terms of budget and schedule, yes. But scope creep also "means we are incorporating the new knowledge, and making progress towards delivering the right [solution]" (Siddharta, 2010, pg 1).

    Jessica

    Siddharta. (2010, February 19). [Web log message]. Retrieved from http://toolsforagile.com/blog/archives/236/is-scope-creep-bad

    ReplyDelete
    Replies
    1. Hi Jessica,

      I would agree that for this project some scope creep really did prove to be beneficial. By adding the extra publishers late in the process, we ended up getting what we really wanted to fill the criteria established by the committee. Because the district leadership was willing to be flexible with the timeline, we could afford the scope creep, and use it to our advantage.

      Thanks,

      Genise

      Delete
  2. Genise,

    Your example was chilling and typical (based on my experiences with projects). It only serves to exemplify how important it is to meet and create a Project Charter complete with a Scope Statement, WBS, schedule and budget once the project team has been selected.

    Portny et al. (2008) state that project creep is the result of trying to further improve a project’s outcome by adding activities that were not originally planned. Your case shows how that can run rampant. As the project progressed more and more was added. It takes a Project Manager (PM) to stand firm and say that unless the project team wants to amend or change the project charter and scope and go through the approval process again, that the proposed activities will not be added.

    References

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

    ReplyDelete
  3. Hi Genise,

    Thank you for an inside look at part of the approval process for new curriculum. It is a tedious and arduous task and you and your team are to be commended for sticking through it to the end. While the scope of the project did creep, I tend to agree with you that this may not have been all bad. At least in this situation the predominant sources of scope creep were from additional requirements and requests by what would be considered upper-level management. The only problem I could see would have been if some of the district level supervisors had been upset over the delay. As this didn't happen, there is no need to worry about it. However, it might have been a good idea to get something in writing indicating the change from the original project. Budrovich recommends getting, "decisions from stakeholders formalized and in writing so that you always have proof that you did make a controversial decision on your own" (Laureate Education, Practitioners Voices, You can’t win them all, 2010).

    Thanks again for an interesting and thorough look at this process.

    – jeff

    Reference:

    Laureate Education, Inc. (Producer). (2010). Practitioner voices: You can’t win them all. Budrovich, V. [Video webcast]. Retrieved from https://class.waldenu.edu/webapps/portal

    ReplyDelete
  4. I have no experience with the teaching side of things, so it was interesting to see what all goes into this type of thing. I imagine that a project would not be a project without some type of scope creep and it is fantastic that we are all getting a taste of what to look for should we be involved in a project going forward.

    ReplyDelete