How to depict CSW quarterly plans using Agilefant

Demo @ Cloud Q1 review15.3.2011

Jarno Vähäniitty (jarno.vahaniitty@aalto.fi)Ville Heikkilä (ville.heikkila@aalto.fi)Software Process Research GroupSoberIT

Why?

VisibilitySo that everyone can see – at least

for the short term – who are collaborating on what

What is the Product Backlog?• List of ”everything that needs to be done”

– but idea pool kept separate

• Transcends any single release; sections:– Ongoing iteration– Up next– Ongoing release– Future releases

• Prioritized & elaborated just-in-time– Driven by vision => product & business goals– Ongoing iteration / Immediate future

• Ordered sequentially• Estimated in man-hours

– Further ahead• Estimated in abstract units• Order ”less sequential”

Iteration

Release

Later

2nd release

3rd release

Product vision

Done so far

vs. drives planning

4th release

Idea pool

Roadm

ap

Next up

This is to be kept up-to-date in Agilefant

Agilefant should contain1) All ongoing ”threads of

collaboration” per quarter2) The goal of each”thread” for that

quarter ”on a single line”

In agile terms:All ongoing sprints, their goals &

involved team/product owner pair(s)

”Product” in AF = Work Package

”Project” in AF = Quarter

”Iteration” in AFa thread of research collaboration

”Label” in AF= To which CSW project plan document tasks/deliverables this thread of collaboration contributes to

Story = Concrete description of planned action for that quarter

People responsible for the story

Lots of other features –

ignore them for now

Agilefant instructions available in Cloud SW intranet