 |
| "Fighting for the chance to be heard amongst the experienced" |
As defined by Portny, Mantel,
Meredith, Shafer, Sutton, and Kramer (2008), a scope creep is any individual,
whether clients or team members, who suggests additional aspects of a project,
in an attempt to create a better end result as the project progresses. Not
having played an official role in project management or instructional design
has left me at a great disadvantage, and many of my experiences have occurred during
group projects or random volunteer work at my place of employment. For this
post, I will be basing my experience on a group project I was assigned to last
year for an instructional design course I previously took.
For this particular
assignment, the class was divided into groups to build a lesson plan based on
the A.D.D.I.E. Model, and although each individual was assigned to a specific
process, each week there would be a project leader responsible for compiling
all of the work submitted and organizing the assignment to be submitted. My group
particularly, was made up of five individuals who all had different experience levels
in the field, but unfortunately two of those individuals dropped out leaving a
strain and double assignments for the rest of the group.
Even though we were give a
specific model to follow, there was a constant power struggle between the
experienced, who wanted to format the project based on what they believed was
right and the inexperienced, who wanted to adhere to the requirements and build
the project based on what was outlined in the course instructions. Through each
phase of the project, a scope creep issue that continuously occurred was the
experienced IDers attempt to add more to the project that was initially agreed
on. In one instance, although a specific topic was chosen for the overall
project, as the team developed each stage of the A.D.D.I.E process, there was
one particular team member who wanted to either add additional material for
discussion or include design elements that would extend the project beyond the
five weeks we had to develop it.
While it was understood and
respected that the experienced IDers opinions were valued, the overwhelming
wealth of information was making the process painstakingly difficult for the
inexperienced IDers. At first, every time an additional concept was suggested, everyone
in the group would have constant arguments about the “correct” way of
completing each phase of the project with little resolution. There came a point
where the project was not being completed in a timely manner because there was
a breakdown in communication and rather than consult with each other on
submissions, additions were included without prior approval or consult with other
team members. At the time the project occurred, I believe that each individual
was concerned with what they submitted rather than focusing on the project as a
whole unit.
Managing a project comes with
a lot of responsibility, and if not handled correctly, team members can feel
dejected and the project may not be successful. With the knowledge I have
gained from this course, I have realized how important effective communication
is when combating a scope creep. Stolovitch (n.d.), acknowledged that the scope
creep can potentially veer a project off track, however suggests communicating
with the scope creep that while their additional input is valid, the add-ons
would not fit that particular phase of the project and show a change in scope
will affect the overall timeline of the project. Communicating long distance is
already challenging, but with Stolovitch’s advise, if all team members would
have set aside adequate time for communicating outside of submission days, I
believe these issue would have been minimized. Looking back, to properly manage the scope creep,
I should have a detailed outline of why the suggestions would have been detrimental
to the project and hosted a chat or Skype meeting with each team member
present.
References
Laureate Education
(Producer). (n.d.). Project management concerns: ‘Scope creep’ [Video
file]. Retrieved from https://class.waldenu.edu
Portny, S. E., Mantel, S. J.,
Meredith, J. R., Shafer, S. M., Sutton, M. M., and Kramer, B. E. (2008).
Tracking progress and maintaining control: Monitoring project performance and achieving
desired results. In Project management:
Planning, scheduling, and controlling projects (pp. 350). Hoboken, NJ: John
Wiley & Sons Inc.