[TYPO3-team-core-v5] Fwd: Scrumify Phoenix - next steps

[Daniel Pötzinger]

Hey all

Thanks robert for wrapping this up - the ideas sound all good for me and we should give it a try.

I added the DoD from the meeting to the wiki
http://forge.typo3.org/wiki/typo3v5-core/Definition_of_Done

and as well some notes to scrumify phoenix in common
http://forge.typo3.org/wiki/typo3v5-productowner/Scrumify_Phoenix

Looking forward to Sprint Planning 1 at the 16.4. 

Greetings

Daniel

> 
> 
> Am Apr 6, 2010 um 18:49 PM schrieb Robert Lemke:
> 
>> Hi folks,
>> 
>> today I spent for wrapping up the meeting and planning the next steps for our first sprint. Over Easter I have made up my mind about the new approach we're taking and I like it very much. Although I'll surely spend most of my time as a member of the development team, I still see myself being part of the Product Owner team and formally as the v5 team leader. However, if you have any suggestions or ideas I'm of course open for your input.
>> 
>> As you know I'm a bit under time pressure due to the Conference app, so I tried to keep my focus on the most important tasks. If I had more time (some weeks or so) I'd love to write a manual about the TYPO3 project as a whole, but well ...
>> 
>> Today I mainly prepared forge so it can act as a tool for us during the first sprint. I imagine that certain aspects of my setup need some further explanation but you probably get the rough idea when you look at it and keep the Scrum techniques in the back of your mind.
>> 
>> The "TYPO3 Phoenix" project [1] is the umbrella project and starting point for those who are interested in the progress of the project. Members listed on this page are considered to be "part of the TYPO3 Phoenix project team". There are currently four sub projects, namely the Core Team, the Product Owner Team, the Scrum Master and the UI/UX Team.
>> 
>> @Jens: does it make sense to have the UI/UX team / project here because it contains v5 specific content or would you rather like to refer to the HCI project [2]? 
>> 
>> Here's how I imagine that we use Forge for a Scrum sprint lifecycle:
>> 
>> The Product Owner Team maintains the product backlog. How they manage the product backlog is not so important, however, my suggestion is to create Stories as issues in the issue tracker of the Product Owner project and use the category field for relating stories to epics (category = epic). Here's an example for a story: http://forge.typo3.org/issues/show/7144 . So, as I said, it's not important where you keep the product backlog.
>> 
>> Now, during the sprint planning, the Product Owner Team (POT) selects one or more stories for the Sprint Backlog. In Redmine lingo that means: you move the "story" issue from the "Product Owner Team" project to the "TYPO3 Phoenix" project and set the "target version number" to the desired sprint.
>> 
>> As an example you can see two stories which have been moved to the umbrella project and are scheduled for sprint #1:
>> 
>> http://forge.typo3.org/projects/roadmap/typo3-v5
>> 
>> The "Core Team" [3] is the Scrum Team. During the sprint planning and during the sprint the core team members will create smaller tasks which are related to the stories of the sprint backlog. Here's a sample task:
>> 
>> http://forge.typo3.org/issues/show/7145
>> 
>> @Christopher: The drawback here is that we need to create redundant versions in the container project (Phoenix) and the Core Team project - and probably even elsewhere. Therefore it would probably be nice to have some first class sprint support in the future instead of misusing the version field.
>> 
>> During the sprint the Core Team members work on the tasks in their own issue tracker. This is practically the white board with the sprint backlog tasks which move from left to right – to be done, in progress, done.
>> 
>> If problems arise, the Core Team members open a ticket in the Impediment tracker of the Scrum Master project [4]. Ben can then take a look at the incoming issues and take care of them.
>> 
>> During the sprint review, the POT finally (hopefully) accepts the result of the sprint and sets the status of the Story tickets to "done".
>> 
>> Before, during and after the sprint we use the various wiki pages of the projects to keep track and organize things. For example, I created a list of persona in the POT wiki [5]. I suggest that we always link to these roles when we refer to them in the text of a story.
>> 
>> @Jens: Can you update them?
>> 
>> Well, that's it about Forge, roughly. I hope you made it through to the bottom of this email.
>> 
>> As the next steps I suggest the following:
>> 
>> - discuss my proposal, if you like
>> - together with Ben I'd prepare some announcement until end of this week which tells about our last meeting and our future plans
>> - we fill Ben's impediment tracker with tasks we need to solve before the first sprint (no worry Ben, you may delegate a few tasks ;-)
>> - we need to fix a date for the (online) sprint planning
>> 
>> Various important stuff:
>> 
>> - please let's continue the communication in the v5 core team list [6]. If you're not yet subscribed to the list, please do it now
>> - Daniel, Jürgen, Jens and also Björn: you need to sign the CLA [7] now and fax it to the T3A.
>> - Jochen & Nils: do you have the time and will to actively participate in this project? If not I'd remove you from the list for now and you can join back in anytime in the future
>> - Daniel: what's your typo3.org username, is danielp correct?
>> - TWIMC: please upload a proper image of yourself to your typo3.org FE profile and set your true first name and last name
>> 
>> Anything else?
>> I hope my mail client doesn't crash now when I submit the send button ...
>> 
>> Cheers,
>> robert
>> 
>> [1] http://forge.typo3.org/projects/show/typo3-v5
>> [2] http://forge.typo3.org/projects/show/hci
>> [3] http://forge.typo3.org/projects/show/typo3v5-core
>> [4] http://forge.typo3.org/projects/typo3v5-scrummaster/issues
>> [5] http://forge.typo3.org/wiki/typo3v5-productowner
>> [6] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5
>> [7] http://typo3.org/about/licenses/
>> 
>> 
>