Scope Creep



As an undergrad Education student, I was asked to design my ideal classroom along with a team of three members, and teach a lesson along with it. This project encompassed many different steps. We were asked to write out a project plan, create a drawn blueprint of it, create a shoebox model of it, and then actually create the live classroom. The classroom, resources, and/or supplies for the lesson were supposed to only be enough for the professor, and the other classmates.

Well, before I knew it all of the professors that were a part of the Education Department and students from all over the campus decided they were going to come because they had been hearing so much about the project and the many things we had planned for our lesson. The lesson was only supposed to be thirty minutes long, but because so many people were talking about it, we were asked to stretch the lesson out over the course of a week and to make sure that there was going to be enough resources for the faculty and students that would be coming to observe and participate in the learning experience. Well, as we were going purchasing resources more and more people were being added to the guest list and anybody could walk in to enjoy the festivities.

Well, how do you plan for something like that? How do you know that the people that say they are coming will actually show up? It’s definitely not guaranteed. I wanted to create a guest list or a RSVP event. Of course the professor was against it because she wanted everyone to be welcomed to join in on the festivities. I wasn’t trying to keep anyone from coming; I only wanted to ensure that we would have enough food for our “A Taste of Food from Around the World” lesson for Social Studies, activities for our Language Arts Module, and games for our Arithmetic games.

The outcome was that we over purchased items and everyone was able to take plates of food home for later, and we were out of money because we couldn’t return the other items we had purchased. The great part about it was that everyone enjoyed themselves and our project turned out great.

Picture retrieved from:


WK5Assgn: Estimating Costs and Allocating Resources

Develop realistic, data-driven cost and schedule estimates.

One of the resources I found that is supposed to be useful when estimating cost, effort, and activity duration is called SLIM Estimate. “SLIM-Estimate is a resource that is used to estimate the cost, time, and effort required to satisfy a given set of system requirements and determine the best strategy for designing and implementing your software or systems project” (Quantitative Software Management, Inc., 2013). This resource in conjunction with QSM database ensures that the estimations are accurately estimated.

This program seems to be a good resource that will be easy to use, and basically does everything an instructional designer would need it to do. This site has a demo that shows you the different uses of this program, they have the option of doing the SLIM product tour, and it also has the option of doing a conference meeting that will show you how to check estimates to make sure they are valid. I think the demo, tour, and the option of having someone that is willing and able to help show you how to use the product is definitely helpful. I think it helps to ensure proper and successful use of the product.

Total Metrics Logo

The other resource I found is Total Metrics Scope Project Sizing 4.1 Software. This product seems to have many uses and capabilities for every aspect of designing no matter what phase your project is in. It can be used to get project estimates, monitor scope creep, negotiate price variations between the supplier and client, and monitor the completion of each step, estimate effort hours, and many more functions. These are all projected benefits for this software given by the website.

After watching the demo of this product and seeing that it has some tutorials to show you how to maneuver through the site just like SLIM estimate, makes me feel like it is also another pretty good resource. It has many uses such as “graphically model software functionality from planning through to production and support, quantitatively tracks multiple change requests within a release to give early warning of potential project blow-outs, allows for very accurate detailed counting, linking each process to each data element and file for quantifying scope variations in a contract” (Total Metrics), and many more uses.


Quantitative Software Management, Inc., (2013). Retrieved from:

Total Metrics. Retrieved from: