|Project Management System|
The product development cycle varies from organization to organization but typically resembles the following. The phases and sequence illustrated here are given to illustrate how ProjectLight® fits into a project development cycle. It is expected that elements will be revisited and updated throughout the product development.
Some of the elements are specific to following ISO procedures and/or risk management. Even if these are not required for your project you can still use ProjectLight® to ensure that a quality product is delivered on time by not utilizing them or only using those fields that are relevant to you. For example for ISO 9001, corrective actions and preventative actions require specific information and tracking during the observation, action and verification phases of their lifecycle.
Although not explicitly mentioned here, tasks and meetings may be created to perform all the above, not just the implementation and testing. Any of these may be flagged as being SR&ED eligible.
Milestones are created to indicate the desired completion dates. Those assigned to perform tasks should immediately indicate the estimated time required to perform those tasks so that ProjectLight® can report on current estimates for meeting the various milestones. The time spent and estimated time to complete should be updated regularly so that ProjectLight® may create automatic ('weekly') status reports for team members and update milestone status. The project leader can use the project, task and timeline tools to re-assign tasks or make other adjustments to keep the project on track.
For ISO it is required to create change notices for requirement changes or additions after the requirements have been locked down.
Scrum is an iterative incremental process of software development commonly used with agile software development. Here is an overview of how scrum works:
During each sprint, a 15-30 day period (length decided by the team), the team creates an increment of potentially shippable (usable) software. The set of features that go into each sprint come from the product backlog, which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting. During this meeting the Product Owner informs the team of the items in the product backlog that he wants completed. The team then determines how much of this they can commit to complete during the next sprint. During the sprint, no one is able to change the sprint backlog, which means that the requirements are frozen for a sprint.
Here is how ProjectLight® can be used with Scrum: