Update from the Sakai Requirements Working Group. Mark Norton Mara Hancock. The REQ-WG The Requirements Process Current Status Going Forward. Overview. Formed in Aug. of 2005 to gather inputs into the Sakai development process.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
The group has about 8 active members who meet regularly to review new inputs.
Group participation is open to anyone so please join in!The Requirements WG
Review and cluster incoming requests.
Manage the community ranking process.
Assist Chuck and Peter in engaging developers to work on priority items.Responsibilities
Let’s look at the requirements part of the process more closely ….
A form (like the one on the next slide) is used to capture your requirements information.
This approch allows Sakai to track the suggestion all the way through to implementation and bug fixing.Register Requirements
Duplicates are merged.
Submissions are sorted into on of serveral categories for tracking purposes.
Bugs are forwarded to Peter for handling.Review Submissions
This gives everyone a chance to indicate which suggestions should be worked on.
The next round of prioritization will be in Feb/Mar of 2007.Prioritize Requirements
Several requirements have led to important changes in Sakai, such as time release and ordering in the Resource Tool.
More work to do, but suggestions are always welcome!Status
A central collection of all requirements is being made in confluence.
The requirements process is the first step in the overall Sakai development process.Going Forward