Editing Task:Sprint progress

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.

Learn more about Contributing to the wiki.

==The problem: progress unknown==
maemo.org is being developed through public sprints since February 2008. The parties involved are the maemo.org funded crew, the Nemein guys in charge of the Midgard CMS and the Nokia contacts.

In every sprint planning meeting each one of us has committed to a lot more than at the end was completed. This is not a problem per se (it usually happen, apparently). The problem is the lack of shared information about the progress on tasks and the reasons for the delays.

This leads to common issues like:
* Not knowing whether a task is stuk or the responsible is working on it, just not reporting progress.
* Not knowing whether a task apparently stuk will be addressed anytime soon or will drop to the next sprint.
* Not knowing whether a task could get help from others, including people external to the core team.

According to previous agreements, everybody should send weekly reports to the mailing list. In practice only few people has done it few times.

==The proposal: adapt scrum==
In fact these problems are well known in project management, specially in distributed environments. Agile development fights this lack of information with e.g. a daily short scrum meeting and a table showing the progress of all committed tasks.

===First of all: documented tasks===
Documenting is always good, but in our case is essential. A written description of a task is the first and best element to ensure that everybody agrees on the same. We owe transparency to the Maemo community and we want to receive their help whenever possible. Tasks can be started by one person and continued by others. At any time a team member might want to know abous a specific task and s/he can't go to the office of the co-worker and ask.

All this leads to documenting tasks properly. 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]] 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].

'''Proposal''': No new tasks accepted in the Backlog after Sprint2 unless they are backed by a decent wiki page or bug report.

===Second: daily microreports===
Daily standup scrum meetings when working online is difficult.  ;)  Instead, it's easy to update (ideally daily) your status in a wiki page by telling in 3 sentences:
# What have I done since my last report.
# What are the obstacles I'm facing.
# What is the plan until the next report.

'''Proposal''': Start this practice in Sprint2.

===Third: progress table===
We can skip time allocation and nice graphical burn-down charts :) but it would be useful to have a simple table showing
* Task
* Owner
* % of completion, or even a simple e.g. "Not started", "Started", "Ongoing", "Almost complete", Complete".

for all the tasks involved in a sprint. This way it would be easy to see in a first glance where are the green and red areas.

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Task (view source) (semi-protected)

Retrieved from "http://wiki.maemo.org/Task:Sprint_progress"

Personal tools

Navigation

Views

Editing Task:Sprint progress

@@ Line 1: / Line 1: @@
-{{task|completed}}
+{{task|ongoing}}
-You can follow the first iteration at [[100Days/Sprint2]]
+==The problem: progress unknown==
-==The Problem: Progress Unknown==
 maemo.org is being developed through public sprints since February 2008. The parties involved are the maemo.org funded crew, the Nemein guys in charge of the Midgard CMS and the Nokia contacts.
@@ Line 9: / Line 7: @@
 This leads to common issues like:
-* Not knowing whether a task is stuck or the responsible party is working on it and just not reporting progress.
+* Not knowing whether a task is stuk or the responsible is working on it, just not reporting progress.
-* Not knowing whether a task apparently stuck will be addressed anytime soon or will drop to the next sprint.
+* Not knowing whether a task apparently stuk will be addressed anytime soon or will drop to the next sprint.
 * Not knowing whether a task could get help from others, including people external to the core team.
-According to previous agreements, everybody should send weekly reports to the mailing list. In practice only few people have done it and only a few times.
+According to previous agreements, everybody should send weekly reports to the mailing list. In practice only few people has done it few times.
-==The Proposal: Adapt SCRUM==
+==The proposal: adapt scrum==
-In fact these problems are well known in project management, especially in distributed environments. Agile development fights this lack of information with a daily short scrum meeting and a table showing the progress of all committed tasks.
+In fact these problems are well known in project management, specially in distributed environments. Agile development fights this lack of information with e.g. a daily short scrum meeting and a table showing the progress of all committed tasks.
-===Document tasks===
+===First of all: documented tasks===
-Documenting is always good, but in our case it is essential. A written description of a task is the first and best element to ensure that everybody agrees on the same plan. We owe transparency to the Maemo community and we want to receive their help whenever possible. Tasks can be started by one person and continued by others. At any time a team member might want to know about a specific task and they can't go to the office of the co-worker and ask.
+Documenting is always good, but in our case is essential. A written description of a task is the first and best element to ensure that everybody agrees on the same. We owe transparency to the Maemo community and we want to receive their help whenever possible. Tasks can be started by one person and continued by others. At any time a team member might want to know abous a specific task and s/he can't go to the office of the co-worker and ask.
 All this leads to documenting tasks properly. All tasks willing to be commited in a maemo.org sprint should have either:
@@ Line 27: / Line 25: @@
 '''Proposal''': No new tasks accepted in the Backlog after Sprint2 unless they are backed by a decent wiki page or bug report.
-===Daily microreports===
+===Second: daily microreports===
-Having daily standup scrum meetings when working online is difficult.  ;)  Instead, it's easy to update (ideally daily) your status in a wiki page by telling in 3 sentences:
+Daily standup scrum meetings when working online is difficult.  ;)  Instead, it's easy to update (ideally daily) your status in a wiki page by telling in 3 sentences:
-# '''What have I done since my last report.''' This is useful for others to see what is the progress.
+# What have I done since my last report.
-# '''What are the obstacles I'm facing.''' This is useful to highlight problems (e.g. non-evident dependencies) where others can help.
+# What are the obstacles I'm facing.
-# '''What is my plan today.''' This helps you to get organized and provides an orientation to others working in related tasks.
+# What is the plan until the next report.
 '''Proposal''': Start this practice in Sprint2.
-===Progress table===
+===Third: progress table===
-We can skip time allocation and nice graphical burn-down charts, :) but it would be useful to have a simple table showing the basic information for all the tasks involved in a sprint. This way it would be easy to see in a first glance where are the green and red areas.
+We can skip time allocation and nice graphical burn-down charts :) but it would be useful to have a simple table showing
+* Task
-{| class="wikitable sortable"
+* Owner
-|-
+* % of completion, or even a simple e.g. "Not started", "Started", "Ongoing", "Almost complete", Complete".
-! Committed
-! Task
-! Owner
-! %
-! Highlights
-|- style="background:LightGreen"
-| 2008-06-24 || Task D || Miguel || '''DONE''' || LightGreen = Completed
-|- style="background:LightBlue"
-| 2008-03-21 || Task B || Micaela || 50% || LightBlue = Good progress
-|-
-| 2008-02-20 || Task A || Mika || 50% || Default = Just standing
-|- style="background:Orange"
-| 2008-04-22 || Task C || Michael || 50% || Orange = Some help needed!
-|- style="background:Tomato"
-| 2008-05-23 || Task D || Michelle || 50% || Tomato = Really stuck/delayed
-|}
-[[Category:Community]]
+for all the tasks involved in a sprint. This way it would be easy to see in a first glance where are the green and red areas.
-[[Category:maemo.org]]
-[[Category:Sprints]]