Editing Maemo.org sprints
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{{lowercase}} | {{lowercase}} | ||
- | + | maemo.org development is handled through a [http://en.wikipedia.org/wiki/SCRUM scrum] process with a monthly planning meeting held on [[IRC]] in [irc://chat.freenode.net/maemo-meeting #maemo-meeting], and daily status reporting and task-specific progress reporting on that Sprint's wiki page. | |
- | Anyone interested in following the maemo.org development process should review the [[ | + | Anyone interested in following the maemo.org development process should review the [[maemo.org Sprints/November 08|current month's]] Sprint page and consider attending the [[IRC]] meeting. |
== Process == | == Process == | ||
- | The | + | The sprint process is adaptable and simple, with a large part of its appeal being the ease with which newcomers can pick up the process. |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
=== Sprints === | === Sprints === | ||
- | <small>''Note: | + | <small>''Note: The first 5 Sprints were under the [[100Days]]. Sprint 1 was handled internally.''</small> |
Development is broken down into monthly sprints with an [[IRC]] review and planning meeting at the beginning of the month of each sprint. | Development is broken down into monthly sprints with an [[IRC]] review and planning meeting at the beginning of the month of each sprint. | ||
Line 22: | Line 15: | ||
These are all of the previous Sprints: | These are all of the previous Sprints: | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
* [[maemo.org Sprints/November 08|November 08]] | * [[maemo.org Sprints/November 08|November 08]] | ||
* [[maemo.org Sprints/October 08|October 08]] | * [[maemo.org Sprints/October 08|October 08]] | ||
* [[100Days/Sprint5|Sprint 5]] | * [[100Days/Sprint5|Sprint 5]] | ||
- | |||
* [[100Days/Sprint4|Sprint 4]] | * [[100Days/Sprint4|Sprint 4]] | ||
* [[100Days/Sprint3|Sprint 3]] | * [[100Days/Sprint3|Sprint 3]] | ||
Line 56: | Line 25: | ||
* [https://garage.maemo.org/plugins/wiki/index.php?April2008Sprint&id=106&type=g April 08] | * [https://garage.maemo.org/plugins/wiki/index.php?April2008Sprint&id=106&type=g April 08] | ||
* [https://garage.maemo.org/plugins/wiki/index.php?Sprint3Tasks&id=106&type=g February & March 08] | * [https://garage.maemo.org/plugins/wiki/index.php?Sprint3Tasks&id=106&type=g February & March 08] | ||
- | |||
=== Tasks === | === Tasks === | ||
- | |||
- | A written description of every proposed and committed task for maemo.org will be provided in a wikipage | + | A written description of every proposed and committed task for maemo.org will be provided in a wikipage for that task. This ensures that everybody agrees on the same plan for the task, and provides a centralized place to track the specifics of the development of that task. |
All tasks willing to be commited in a maemo.org sprint should have either: | All tasks willing to be commited in a maemo.org sprint should have either: | ||
- | * [[:Category:Proposed|A proposal]] in a wiki page starting with "Task:" using the [[Template:Task]] | + | * [[:Category:Proposed|A proposal]] in a wiki page starting with "Task:" using the [[Template:Task]] in mode <nowiki>{{task|proposed}}</nowiki>. |
- | + | * Or a bug report in product Website with [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=Medium&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Medium priority]. | |
- | * Or a bug report in | + | |
Only tasks with wiki pages can be committed for a Sprint. | Only tasks with wiki pages can be committed for a Sprint. | ||
- | |||
- | |||
=== Planning meeting === | === Planning meeting === | ||
- | The planning and review meeting is held | + | The planning and review meeting is typically held at the beginning of each month, and is usually scheduled after some discussion on the [https://lists.maemo.org/mailman/listinfo/maemo-community maemo-community] mailing list. Reviews typically last between 2 and 4 hours, so attendance may not be possible for everybody, but [http://maemo.org/maemo-meeting/ logs are posted to the website] usually by the next day. |
The channel is unmoderated for the duration of the meeting, but extraneous and off-topic comments and conversation must be kept to an absolute minimum (#maemo can be used for chatter). There is a lot of information being exchanged between a lot of different people, and chatter slows us down and confuses the meeting. | The channel is unmoderated for the duration of the meeting, but extraneous and off-topic comments and conversation must be kept to an absolute minimum (#maemo can be used for chatter). There is a lot of information being exchanged between a lot of different people, and chatter slows us down and confuses the meeting. | ||
Line 82: | Line 46: | ||
Direction of the meeting is typically handled by either Nokia's community representative or one of the [[Community Council]] members (depending on who is available). | Direction of the meeting is typically handled by either Nokia's community representative or one of the [[Community Council]] members (depending on who is available). | ||
- | + | Actions to be taken before the meeting to save IRC time: | |
- | * | + | * Meeting facilitator creates new sprint page and links it to the sprint meeting announcement. |
* Task owners leave the final status of their tasks in the sprint: | * Task owners leave the final status of their tasks in the sprint: | ||
- | ** | + | ** DONE (green background) or % of completion (red background). |
** Comment for posterity summarizing what was done/left. | ** Comment for posterity summarizing what was done/left. | ||
- | ** Update the status banner of the wiki task page | + | ** Update the status banner of the wiki task page. |
- | * Facilitator moves all the | + | * Facilitator moves all the uncomplete tasks to the table of the new sprint. |
- | * Anybody willing to propose a new task needs to list it in the | + | * Anybody willing to propose a new task needs to list it in the Proposals page. |
* Anybody willing to push a bug needs to get it to MEDIUM priority (request it in the bug itself if you don't have permissions). | * Anybody willing to push a bug needs to get it to MEDIUM priority (request it in the bug itself if you don't have permissions). | ||
Meeting agenda: | Meeting agenda: | ||
- | # | + | |
- | ## Only general/exceptional comments, since the | + | # Revision of the past sprint: |
- | ## Any | + | ## Only general/exceptional comments, since the revision as such is left in the table and daily reports. |
- | # Planning of the | + | ## Any task marked as "DONE" considered by anybody not completed? |
- | ## Any task moved from the previous sprint considered not appropriate for the new sprint e.g. better | + | # Planning of the new sprint: |
- | ## Tasks from the backlog | + | ## Any task moved from the previous sprint considered not appropriate for the new sprint e.g. better back to the backlog or dropped? |
- | ## Tasks from the Proposals page | + | ## Tasks from the backlog committed. |
- | ## Any pending HIGH bugs to be dropped to MEDIUM | + | ## Tasks from the Proposals page committed, to the backlog or sent back for improvement. |
+ | ## Any pending HIGH bugs to be dropped to MEDIUM/LOW/wontfix? | ||
## Any MEDIUM bugs promoted to HIGH and committed to the sprint? | ## Any MEDIUM bugs promoted to HIGH and committed to the sprint? | ||
- | Just to clarify: no new tasks and no LOW bugs taken if they were not proposed/promoted before | + | Just to clarify: no new tasks and no LOW bugs taken if they were not proposed/promoted before. You can always work on them out of the official sprint. |
Actions to be taken after the meeting: | Actions to be taken after the meeting: | ||
* Update the tasks and bugs tables according to the meeting agreements. | * Update the tasks and bugs tables according to the meeting agreements. | ||
* Upload meeting log and link it from the new sprint page. | * Upload meeting log and link it from the new sprint page. | ||
- | * Review old and new committed task pages | + | * Review old and new committed task pages making sure they have the correct status banner. |
=== Daily reporting === | === Daily reporting === | ||
- | Having daily standup scrum meetings when working online is difficult, so, Instead, developers involved in the Sprint will report their daily progress (assuming they're working on anything Maemo-related) | + | Having daily standup scrum meetings when working online is difficult, so, Instead, developers involved in the Sprint will report their daily progress (assuming they're working on anything Maemo-related) on the month's wiki page in 3 sentences: |
- | + | # '''What have I done since my last report.''' This is useful for others to see what is the progress. | |
- | + | # '''What are the obstacles I'm facing.''' This is useful to highlight problems (e.g. non-evident dependencies) where others can help. | |
- | + | # '''What is my plan today.''' This helps you to get organized and provides an orientation to others working in related tasks. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
The reports are necessary for other developers and interested community members to be able to follow the Sprint's progress, so reporting is ''highly'' recommended for paid contributors, and suggested for volunteers. | The reports are necessary for other developers and interested community members to be able to follow the Sprint's progress, so reporting is ''highly'' recommended for paid contributors, and suggested for volunteers. |
Learn more about Contributing to the wiki.