HeaderSIS.jpg

IS480 Team wiki: 2012T1 Timber Werkz ProjectScope

From IS480
Jump to navigation Jump to search
HOME   PROJECT
DESCRIPTION
  PROJECT
MANAGEMENT
  DOCUMENTATION   RESEOURCES LEARNING
EXPERIENCES
PROJECT FRAMEWORK PROJECT SCOPE MILESTONES METRICS RISKS & MITIGATION



Project Scope



A complete and detailed list of the project scope is shown in the Product Backlog.


Main features the Product Backlog


An Extract of the Product Backlog


The product backlog consists of “stories”, or the smallest unit of delivery of a particular use case. Each story has a short description to it, and is assigned a specific priority. In descending order, the priority levels are: Must, Should, Could, and Won’t. This guides us in scheduling our sprint according to priority. There is also the level of complexity, and doubt, which helps us to identify which stories are of higher risk than others, and decide if a proof-of-concept should be carried out to ensure that the technology and environment in use is able to support the client’s requirements.


On top of that, the product backlog also shows the current status of the story - whether it is pending elaboration from the client (at the stage of doing UI mockups and requirements gathering), pending development, in development, pending approval from the client (upon completion of development), implemented (but still on the development environment), live (in production environment), fixing, or withdrawn.


Lastly, the product backlog displays the estimated man-hours required and the prerequisite stories dependency relationships for the particular story and helps to guide the planning of each sprint. At the beginning of each sprint, the product backlog and the list of milestones are referred to, and members will decide which stories to be included in that sprint. Whatever stories or tasks that has not been completed in the previous sprint will be returned to the product backlog and may be attempted in future sprints.