Thursday, February 14, 2013

Analyzing Scope Creep

Project scope is the work that has to occur to deliver a product, service, or result with specified features and functions (Wikipedia, 2013a). Scope creep refers to sometimes-uncontrolled changes in project or course requirements, in addition to continuous growth in a project's scope (Wikipedia, 2013b). Scope creep is commonly caused by new features that are added to the project (Lynch & Roecker, 2007). Scope creep can be beneficial as long as the project team can properly respond sensibly to the project’s changing conditions (Greer, 2010). However, the changes can cause the project to stray from its original obejctives and design. It can also occur when the scope of a project is not properly defined, documented, or controlled.

The project that I am describing occurred in the Intro to Computers & Technology class during my first college semester. We were required to create a PowerPoint presentation about IT and computers, and then explain it to the class. My group consisted of three students: two others and myself as the group leader. However, from the initiation of the project there was a problem with communication. Even though we were in a group, we seldom communicated. As the time approached to gather information, there was little input even after making contact with team members. Consequently, I wound up doing the bulk of the project work to research, compile information, and create slides with graphics for the presentation. The scope creep resulted from lack of communication and underestimation of time. It was not until the final day for completing the project that we eventually met as a group. The result was members hastily putting together their parts of the presentation within a few hours before class. Slides added at the last minute had to be adjusted to fit into the presentation. But because I had done so much of the work already, these last minute revisions created a potential for collapse of the project, or for a completely different version. Also, due to lack of time to properly rehearse my speech, I stumbled occasionally during the presentation. Still, this did not negatively affect my overall performance and grade. I received an A for the presentation and course, respectively. But in my evaluation, the process to complete the project was very inefficient and quite stressful at times.

As the unofficial project manager, in retrospect, I realize the mistakes that I made. I could have insisted on devising times where we could meet in the library, and communicate more often via email and phone. This would have given us the opportunity to keep within the timeline, discuss exactly what information was needed from members, and how their input fit into the presentation. This is an important part of controlling and creating a project, because any proposed changes should be discussed and approved by team members and stakeholders (Lynch & Roecker, 2007).

References:

Greer, M. (2010). The project management minimalist: Just enough PM to rock your projects! (Laureate custom ed.). Retrieved February 14, 2013 from https://class.waldenu.edu/bbcswebdav/institution/USW1/201340_02/MS_INDT/EDUC_6145/Syllabus/Syllabus/embedded/pm-minimalist-ver-3-laureate.pdf

Lynch, M. M., & Roecker, J. (2007). Project managing e-learning: A handbook for successful design, delivery, and management. Retrieved February 14, 2013 from https://class.waldenu.edu/bbcswebdav/institution/USW1/201340_02/MS_INDT/EDUC_6145/Week%206/Resources/Week%206%20Resources/embedded/6145_Wk6_Lynch_Ch5.pdf

Wikipedia (2013a). Scope. Retrieved February 14, 2013 from http://en.wikipedia.org/wiki/Scope_(project_management)

Wikipedia (2013b). Scope creep. Retrieved February 14, 2013 from http://en.wikipedia.org/wiki/Scope_creep

Thursday, February 7, 2013

Estimating Costs and Allocating Resources

Project managers are primarily responsible for developing and producing project budget estimates as well as allocating resources (Portny, Mantel, Meredith, Shafer, Sutton, & Kramer, 2008). A critical part of the project budget is cost estimates, which detail the costs of the resources needed to complete the project tasks (Greer, 2010). After identifying the project tasks, each task in the network diagram should be reviewed according to the resources (people, equipment, and materials needed to complete the task), effort (labor units required, such as staff hours), and duration (the period of time over which the task occurs). Sometimes new project managers can confuse duration and effort. There can also be issues with calculating cost, such as overestimation. These links are intended to help PMs and IDs avoid these issues, as well as enhance their knowledge and understanding of how to complete the aforementioned tasks for projects.

URL: http://www.pmsite.com/Forum/tabid/159/aft/2003/Default.aspx
This link is a message board topic about how the total project cost of the project can be properly distributed to all activities (Tibi, 2012). One of the answerers stated that it is best to build the total cost from the bottom-up. Additionally, there is discussion pertaining to when a top-down method is chosen, involving "lumpsum" resources or an expense item assigned to some of the activities.

URL: http://vandylb6.wordpress.com/2012/11/30/project-schedule-budget-plan-2/
This is a blog that highlights some websites that can help a project manager develop a budget plan (Vandylb, 2012). There is a website developed by the University of Wisconsin provides a template for project management, listing five major steps: conceive, initiate, plan, execute & control, and close. Planning is also divided into a four-stage progression: project kick-off meeting, develop work plan, develop project control plan, and finalize final project plan and gain approvals. Also included is an entry on blog site written by Don Clark pertaining to budgeting for instructional design projects. There is also information about an interesting case study detailing Verizon’s transition to e-learning.

URL: http://www.ukdissertations.com/dissertations/management/cost-management.php
On this blog, cost is described as one of the three pillars supporting project success or failure, along with time and performance (UKDissertations, n.d.). Cost management is described as the process of planning, estimating, coordination, control and reporting of cost-related aspects of the project. There are paragraphs on resource planning, estimating costs, and types of estimating, such as bottom-up estimating, analogous estimating, parametric estimating, design-to-cost estimating. Further information includes tools for analyzing/evaluating cost management, various charts and diagrams that can be used, as well as applying histograms. This site can enable project managers and instructional designers to really understand and help plan a project’s schedule, create a budget, or break down the project’s tasks.

References:

Greer, M. (2010). The project management minimalist: Just enough PM to rock your projects! (Laureate custom ed.). Retrieved February 7, 2013 from https://class.waldenu.edu/bbcswebdav/institution/USW1/201340_02/MS_INDT/EDUC_6145/Syllabus/Syllabus/embedded/pm-minimalist-ver-3-laureate.pdf

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.

Tibi (2012). Total Project Cost. Retrieved February 7, 2013 from http://www.pmsite.com/Forum/tabid/159/aft/2003/Default.aspx

UKDissertations (n.d.). Cost Management. Retrieved February 7, 2013 from http://www.ukdissertations.com/dissertations/management/cost-management.php

Vandylb (2012). Project Schedule & Budget Plan. Retrieved February 7, 2013 from http://vandylb6.wordpress.com/2012/11/30/project-schedule-budget-plan-2/