Design & Development Process » History » Version 3
Tom Clegg, 04/06/2013 06:56 PM
| 1 | 1 | Anonymous | h1. Design & Development Process |
|---|---|---|---|
| 2 | |||
| 3 | 3 | Tom Clegg | The design process for Orvos is based on agile development principles. We maintain a list of all known bugs in the Issues database. The development work is currently organized into 2 week sprints, but contributions are welcome at any time. |
| 4 | 1 | Anonymous | |
| 5 | 2 | Anonymous | The plan for what we build is described in the Backlog of user stories. Anyone is open to contribute user stories by creating a New Issue and making it a story. Please try to write "well crafted stories.":http://www.allaboutagile.com/writing-good-user-stories/ |
| 6 | |||
| 7 | 3 | Tom Clegg | Right now, the engineers at Clinical Future decide which Backlog items go into each sprint. As the community expands, we expect to lengthen sprints, and expand use of IRC and email lists to get a lazy consensus on the backlog for each sprint. Of course, you don't have to work on the Backlog. If some other aspect of the project interests or you want to write other code, go for it. The Backlog is just a suggestion. |
| 8 | 2 | Anonymous | |
| 9 | 3 | Tom Clegg | We are starting to organize the work driving towards releases. Look a the [[Roadmap and Release Plan]] to see what we're currently thinking. We expect to shift to a regular release schedule and use a process of online design summits to decide on release themes. |