Lesson Learned

Team D Lessons Learned

Our project required us to build a website for XYZ daycare to improve information access for current customers. The team was required to identify the specific work to be done for this project. Being unfamiliar with the project, some of the problems we encountered included ambiguity in scope definition, incomplete definition of the scope, and scope creep. Carefully identifying the scope of the project would give us a better understanding of how much time is needed to complete the project, what the deliverables are, how to implement creating said deliverables, and the risks involved with this project. To defend against all of these problems it is best to carefully define the project’s scope at the beginning of the project so that the core team members and the clients understand exactly what needs to get done and a reasonable time frame in which to do it.

The second lesson learned was the use of tools and methods to plan the project. During the planning of the project we leaned the importance of using the Work Breakdown Structure (WBS), providing us with the necessary tool and techniques that allowed us to beak the project into various sub-projects without compromising the goal and objectives that were established at the project kickoff. Using the WBS we were able to derive our measure and tracking of deliverables as well as estimates on the cost and time required to create them.

Another tool that was helpful during the project was the RASIC. The RASIC was used to assign tasks to various individuals involved in the project. When our team analyzed the RASIC we noticed that the website designer was assigned the most task responsibilities; in fact, it was far more than the of the team members. As a team we felt that we needed to better allocate the amount of work being done so as not to overload any one person. Part of the reason for the over allocation was the nature of the project. Most of the work had to do with designing,...