Scope Creep Can be Overwhelming
Reviewing projects post-mortem, or after the finished product has
been delivered has important benefits. Learning from experience can be very beneficial
(Terzieva and Morabito, 2016). Taking the time to develop a list of pitfalls,
can help instructional designers and project managers avoid those same pitfalls
in future projects. For this blog post, the project being reviewed post-mortem culminates
in a multimedia presentation of an organizational profile, including, the
analysis of a change that the organization underwent. For the assignment, it scored high marks.
However, in retrospect, it was not a completed project backed with enough pride
to be included in the instructional design portfolio.
The processes included in the project that were successful were
all related to the analysis phase which included staff interviews. Explanations
of the company culture, which was a school district, the leadership, in this
case, district administration, and the effects of crisis remote teaching during
the pandemic from the teacher’s perspective were done well. Part one of the
deliverable document was comprised of descriptions of the change process, the
resistance encountered, communication strategies, and overall effectiveness.
Part two of the deliverable document was composed of further analysis of the
change and how the leaders planned and implemented the change process. As a
leader, it is always better to gain insight and input from your team before
making big decisions (Schermerhorn et al., 2008). Part three was a 5–7-minute
video presentation. The part one and two deliverable documents were thorough
and rooted in theory. The video presentation had some decent instructional
design components, but overall, was too deep in scope. Conclusions and
recommendations were not clearly communicated because the topic was so broad. Overall,
the multimedia presentation complied with Mayer’s instructional design
principles, such as the principles to reduce extraneous processing including
the coherence, signaling, redundancy, spatial, and contiguity principles (Mayer,
2014).
The change analyzed was crisis remote teaching, which became too
large of a topic. Scope creep set in as a passion for the subject grew in the
design and development phase. Narrowing down the content in the deliverable
analysis documents to create a sound multimedia presentation,
with only 5-7 minutes of viewing time became difficult and frustrating.
Choosing to uncover how crisis remote teaching affected the organization in one
specific area, such as student engagement for example, rather than an overview
of all the effects of pandemic teaching would be a better path to take in
designing a project like this one again. Creating a statement of work (SOW) to
define the project’s approach, deliverables, timeline, and budget, would have
made the end product more successful (Laureate Education, n.d.). Overall, the
final video presentation complied with Mayer’s instructional design principles
in general, but the design could have been of higher quality. Without the scope
creep issue, the content would have been more concise and more time could have
been spent designing and developing the best quality materials.
When looking through the rearview mirror, it is clear that this
project is an example of the negative effects of scope creep. All of the ideas
included in the project are valid and beneficial, however, they should not all
be included in one project. There is enough content for several more projects
when broken down into smaller topics with clearer objectives. Now that an
understanding that scope creep happens frequently has been gained, a plan to
avoid this pitfall with new projects can be created before it ever has a chance
to set in.
References
Mayer, R. E. (2014). The Cambridge handbook of
multimedia learning. The University of Cambridge.
Project
kickoff [Video]. (n.d.). Laureate Education. https://class.waldenu.edu
Schermerhorn,
J. R., Hunt, J. G., & Osborn, R. N. (2008). Chapter 1, "Introducing
Organizational Behavior". In Organizational Behavior (10th ed.,
pp. 4–12). John Wiley & Sons.
Terzieva, M., & Morabito, V. (2016). Learning from
experience: The project team is key. Business Systems Research, 7(1),
1–15. https://doi.org/10.1515/bsrj-2016-0001