[maemo-community] Sprint Task Status Update SSO

From: Jeremiah Foster jeremiah at jeremiahfoster.com
Date: Fri Nov 6 01:17:20 EET 2009
On Nov 5, 2009, at 23:20, Qole wrote:

> Thanks, penguinbait.
>
> I have also struggled to follow what is happening regarding the  
> sprints.
>
> It can be frustrating to see 0% tasks with no comments for me too.
>
> At the very least, could the qaiku #maemork comments always have the  
> task ID? I think non-task "business as usual" (BAU) shouldn't be  
> tagged #maemork. Perhaps a separate channel for task related and non- 
> task related comments?

BAU I think is useful for communicating to other people internally  
what one is doing. Often there are 'blockers', i.e. one waits for  
someone to do A before you can do B. Like I'm watching as the servers  
are being installed before I start testing tools for repo management.

You can search Qaiku based on a specific tag, say 9.10-07, which is  
the server ISP sprint item:
http://www.qaiku.com/search/result/Y29tX3JvaGVhX3NpbXBsZXNlYXJjaA==/1/9.10-07/

As you can see, you get results about that specific item and that  
might be a good way to keep track of that sprint in addition to  
keeping notes on the wiki.

I agree that we need to keep better notes on the wiki, but some of  
this is new to people and some of this is reported elsewhere. I think  
if we had a way to communicate workflow to new council members so they  
new what to expect that would be helpful too - I imagine a lot of this  
is pretty cryptic to those who have not helped design the process.

Some good comments about micromanaging in this email thread! In my  
experience micromanagement seldom leads to the results one hopes for.  
That said, the process not immutable and improvements possible.

Jeremiah

More information about the maemo-community mailing list