[Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement

[Woods, Chris]

Hi Folks,

I've some experience as a scrum master, typically an agile project would be described in differing blocks of granularity. Each block describing the project in increasing detail.
Where a theme breaks down into many epics, which in turn break down into many user stories, which in turn break down into many implementation tasks, effectively a large tree. I've put together the table below, I hope this helps. - I shows how I've broken down agile projects before.

Chris

Title

Theme

Epic

User story / features

Implementation task

Level of detail

Very Low

Low

Medium -functional details provided

High - Implementation details provided

Description

A very high level statement of the project goal.

Many epic's or "scenarios" which many result in the project achieving the goal stated in the theme

Suggested user stories which



Coverage

All functionality

All functionality

All functionality

Only the functionality which needs to be implemented. - These are work items.

If an asset already implements a feature, then there is no need for an implementation task, as this has already been completed.


Examples

Change the way the world consumes music

John, a music lover, really enjoys having access to great music wherever he travels.

Example 1: John, a music lover, packs all of his CDs into a carry case to bring on holiday.
(rejected)

Example 2: John, a music lover, rips his CDs, converting all of them to mp3s and takes them with him on his iPod
(rejected)

Example 3: John, a music lover, subscribes to a service and can stream music to his phone anywhere in the world. Access is provided by an easy to use mobile phone application.
(accepted)

Example 1:
Create a cloud music service at (ilovemusic.fiware.com). Provide a UI with a login button on the top left in bright red with yellow text.... (etc.)..

Example 2:
Produce a design document which outlines the core APIs... (etc)


Typical process



Many epics or scenarios are created. Each epic or scenario is evaluated by team members against the original theme.

Epics are reviewed, some are dropped, others created, and some revised.

The result is a set of epics which the team believe will allow the project to succeed.

Typically an epic will not include implementation detail (unless strictly needed). This allows various user stories to be evaluated against the epic.



For a single epic many user stories will be generated.

Each user story will be reviewed against any criteria specified in the epic.

E.g. does this allow a developer to achieve their goal?

The user stories are updated and reviewed so that only the ones which will best match the epic are accepted by the team.

Typically a user story will contain implementation details.

This allows various implementation ideas to be discussed and evaluated.

A detailed description of the feature, broken down into implementation tasks.

These are tracked on the backlog.

Tasks here can also include "Use asset X to provide core music playback functionality" etc.





From: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of BANNIZA, Thomas-Rolf
Sent: Friday, October 07, 2011 3:53 PM
To: Garino Pierangelo
Cc: fiware-i2nd at lists.fi-ware.eu
Subject: Re: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement

Hi Pier,

 from the pure AGILE point of view, Junajo might be right.

But:

Where is the place where it is really described what a customer (other FiWare WP, use case project) can expect from the GE?
If the EPIC will describe only what's new (or more exact: what still has to be developed), I have seen no place where a comprehensive description of a functionality (new, still to be developed, function together with the appropriately attached assets).

Or did I miss something in this story?

Best regards,
Thomas

________________________________
Von: fiware-i2nd-bounces at lists.fi-ware.eu<mailto:fiware-i2nd-bounces at lists.fi-ware.eu> [mailto:fiware-i2nd-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-i2nd-bounces at lists.fi-ware.eu]> Im Auftrag von Garino Pierangelo
Gesendet: Freitag, 7. Oktober 2011 16:29
An: fiware-i2nd at lists.fi-ware.eu<mailto:fiware-i2nd at lists.fi-ware.eu>
Betreff: [Fiware-i2nd] I: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement
Dear All,
Some further clarification on backlog contents, please take them into account when producing your inputs.
Have a nice weekend
BR
Pier
Da: fiware-wpl-bounces at lists.fi-ware.eu<mailto:fiware-wpl-bounces at lists.fi-ware.eu> [mailto:fiware-wpl-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-wpl-bounces at lists.fi-ware.eu]> Per conto di Juanjo Hierro
Inviato: venerdì 7 ottobre 2011 09:36
A: fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>
Oggetto: [Fiware-wpl] The Backlog is not about describing features that assets being adopted as baseline already implement
Hi all,

  As I have mentioned several times, the Backlog in a product development project is fundamentally about functionality that has to be developed in the product.   Seeking for clarity, and because I have found it helpful when explaining Agile concepts, I have referred to it as "work to be done" because actually what you have to do when developing a software product is developing your functionality.

  On the other hand, we have to deal with a fundamental characteristic of this project: it is not about developing from the scratch but from a baseline formed by selected products (assets) generated in previous projects.   And most of them hadn't been developed using Agile so far.

  If we had developed every GE from the scratch, the backlogs would contain Themes/Epics/Features/User-stories that, all together, would summarize the whole functionality of the GE.  But this is not the case.

  You should consider that the backlog for each and every GE should contain the Themes/Epics/Features/User-stories that, at the current moment, is "pending functionality" (or development) still to be addressed.   It is not the intent that, by reading all entries in the backlog, you should have a complete view on the functionality of the GE.  Someone who wants to have a detailed picture of all target functionality should:

 *   read the FI-WARE Product Vision, in order to understand what is overall expected for the GE
 *   read the documentation available for the baseline assets used for materializing the GE: this should give the reader a clear picture of what is already there
 *   read the backlog, to understand what's going on and is somehow on the roadmap
  The exercise we are doing is about setting the Agile backlogs that will drive our future developments.  It's not about documenting what he have done during many years in our respective labs.

  A last comment: some Agile authorized experts go up to the point that they believe that Backlogs should not only contain info about the functionality to be developed in the product but any "work to be done" by the development team of a product, thus, using Agile for managing every activities in a project.   That's why they mention that entries in a Backlog should be indeed named as "Work Items" rather than "User-stories" ... but that is, of course, a matter of taste.   What is mandatory is to document the Themes/Epics/Features/User-stories that will drive developments on selected assets (this include developments required for integrating the different assets, of course).  This is what should be uploaded on the Wiki and referred from tickets in the "Backlog Management" tracker.   You may create another "Backlog" trackers for additional activities (like documentation, etc.).   That's why I created a "Task Force Management" tracker in addition.

  Remember: Agile is about creating stuff that is useful in the development, not stuff for satisfying reviewers.

  Regards,

-- Juanjo


________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[cid:image001.gif at 01CC850A.1D6865D0]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


-------------------------------------------------------------
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111007/aa8021ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20111007/aa8021ea/attachment.gif>