[almighty] Banksia MVP from the point of view of a Scrum Master

[Michael Kleinhenz]

Hi Ranjith,

great suggestions! I broke them down into epics. See below for comments:

> 1. Be able to define a multiple projects, even if they are isolated from
> each other. Having separate project instances will help the teams to move
> from Trello or any other tool to Almighty

I think this is already covered by #357 and #358.

> 2. Be able to define the concept of Sprint by allowing for a ‘TimeBoxing’
> feature, wherein the team can specify if their Sprints are 1 week or 3
> weeks. So that UX team could also try out the tool.

Iterations are the next topic that we will cover, see the Walking
Skeleton sheet. I created a new epic for this where we can
discuss/source stories from: #378

> 3. Group a subset of user stories into a Sprint backlog after the planning
> session and ability to break down the user stories into tasks, this solves
> one of the biggest pain points with Trello.

Yes, that should be solved by the groundwork with the WILTs and is
ambient for the system. We only have to make sure the UI makes the
connection between "Stories" and "Tasks" clearly visible and
traceable. But I think we're on a good way there.

> 4. We should be able to reflect the progress on a particular user story by
> updating the state of the user story as it progresses.

Already done and in the current implementation.

> 5. We should be able to see different lists like the Product Backlog, Sprint
> Backlog with respect to state. For example to see the user stories that are
> in progress and completed for Sprint 121.

Added that to the iteration epic #378. This one might also be relevant
to the filter epic (#301), because I think the different "views" of
the WIs in the system might only be different applied filters. That
would keep the possible views completely open and flexible while
providing a concise requirement set for the implementation. Also, the
order of execution becomes relevant with that again concerning
possible "local, user-dependent" orders of filtered lists. That might
become a bit complex for the implementation, but if we would have
something like that, it would provide a huge flexibilty for the user.

I added a comment to #301 for that.

> Nice to haves:
>
> 1. Ability to enter estimated story points to the user stories that are part
> of the Sprint Backlog and show the sum of story points taken up in a
> particular sprint.

Added this as a comment to #378.

> 2. Ability to add team members to the project.

That should be coming in as a new story after #357 and #358 are
finished. Added this to #355 (project epic).

> 3. Ability to groups Sprints into a Release. This would allow the teams to
> define Banksia goals in the tool and structure the Sprints accordingly.

That one is a bit nebulous for me. Is a release a WI? I would think it
is based on the current PDD intentions...?

-- Michael

-- 
Michael Kleinhenz
Principal Software Engineer

Red Hat Deutschland GmbH
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany

RED HAT | TRIED. TESTED. TRUSTED.
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill