Difference between Team Requirenment vs Client Requirenment

[ch...@citric.io]

We've been using Taiga for a couple of months now, and it seems we might have the meaning of those 2 options wrong. We assumed team requirement would fit tasks that are needed but not explicitly from the customer (i.e: creating a database) and client requirement would be actual user stories (i.e: logged user can buy products). But since we've been using those options like that, our backlog graphic is kind of weird now and I'm unable to understand it.

Is there any place where the use of those options is documented? if not, can I get a quick explanation? thanks in advance.

Here's a picture of our graph:

[Alejandro Alonso]

Hello!, 

We have to update our documentation to make this two values more  comprehensible

Team requirements that during the project you discover some new user stories that must exist in the project but that will have no cost for the client. For example, a basic feature that must be implemented but that didn't exist at the beginning of the project (probably because the team failed dividing the project in user stories). Team requirements mean "internal" requirements.

Client requirement: for example a new and amazing idea that is absolutely needed for the project but id didn't exist in the beginning ("external" requirement).

The idea of having this two different colours is that if the project grows you can easily distinguish what's the reason.

Regards!,

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/c04a9b5d-90e9-4ef1-a793-e11ffb649a41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alejandro Alonso Fernández   CIO & Co-founder alejandr...@kaleidos.net  | Tel: (+34) 627263808 | (+34) 913562995 www.kaleidos.net/FC8EAC/

[David Barragán]

To understand the "enhanced burndown graph" of Taiga see http://www.mountaingoatsoftware.com/agile/scrum/release-burndown/alternative and http://www.axisagile.com.au/blog/planning-and-metrics/scrum-metrics-and-reporting-measure-what-you-manage/ (Section "Enhanced release burndown"):

Enhanced release burndown

The enhanced release burndown is inspired by Mike Cohn’s ‘Alternative Scrum Release Burndown Chart’.

How is it generated?

1. For each sprint, plot the sum of the ‘remaining points’ for all product backlog items in the product backlog designated for the next release.
2. Draw a trend line relating to the data points in step 1.
3. For each sprint, plot (as negative y-axis values) the sum of the story points for any product backlog items added to the product backlog after the start of the project (if applicable).
4. Draw another trend line that relates to the data points in step 3.

When is this generated?
The enhanced release burndown metric is generated at the end of every sprint.

What is it telling you?
This metric signals what the development team’s rate of progress is relative to the scope’s rate of change. The point where the two trend lines (hopefully) intersect indicates roughly how many sprints will be required to complete the release. If the trend lines run parallel to each other (or diverge), it is an ominous indication that the release will theoretically never see the light of day.

Figure 4 – An enhanced burndown chart, updated after each sprint.

How can you act on it?
If the two trend lines do not intersect or the expected release duration is intolerable, then either the rate of progress needs to increase (by improving practices and / or removing impediments) or the scope needs to be reduced.

Figure 5 – Ominous signs that this release might never see the light of day. Better improve practices, remove impediments, or decrease scope.

On Mon, Sep 21, 2015 at 6:40 PM, David Barragán <david.b...@kaleidos.net> wrote:

Hi Chris,

first of all thanks for using Taiga, and now I'll try to give you some examples about client and team requirements:

client requirements:
 - when you start a project you define some initial user stories (X points in total) in the backlog that represent the grey area in the graph.
 - during the development: user stories are created because your client has a new idea that must be implemented, it affects the backlog because if your compromise is for X points on the project and this user story adds Y points, there are Y points that should be "out" from the original X points. So you need to do X+Y points to finish the project.

team requirements:
- you create the initial backlog for a project but during the development the team discover they need to add a new user story for something they forgot or they didn't consider but they should.

We have to improve our suport pages and add some contextual help messages in Taiga.

Regards!,

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/c04a9b5d-90e9-4ef1-a793-e11ffb649a41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---

David Barragán Merino   Engineer david.b...@kaleidos.net  | Tel: (+34) 913562995 www.kaleidos.net/FFF8E7

--

---

David Barragán Merino   Engineer david.b...@kaleidos.net  | Tel: (+34) 913562995 www.kaleidos.net/FFF8E7

[David Barragán]

Hi Chris,

first of all thanks for using Taiga, and now I'll try to give you some examples about client and team requirements:

client requirements:
 - when you start a project you define some initial user stories (X points in total) in the backlog that represent the grey area in the graph.
 - during the development: user stories are created because your client has a new idea that must be implemented, it affects the backlog because if your compromise is for X points on the project and this user story adds Y points, there are Y points that should be "out" from the original X points. So you need to do X+Y points to finish the project.

team requirements:
- you create the initial backlog for a project but during the development the team discover they need to add a new user story for something they forgot or they didn't consider but they should.

We have to improve our suport pages and add some contextual help messages in Taiga.

Regards!,

On Mon, Sep 21, 2015 at 6:14 PM, <ch...@citric.io> wrote:

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/c04a9b5d-90e9-4ef1-a793-e11ffb649a41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[enriqu...@beeva.com]

Hi David,

We are trying taiga.io, and we have some questions related to team vs client requirements:

- In order to clarify, scrum terminology, team requirements are particular cases of user stories, and not other typical Product Backlog Items as Refactoring or Refinement tasks. Is my assumption correct? Can we include within Taiga arbitrary PBI (no uu.ss) in our product backlog?

- In our last sprint we have tagged some user stories only as team requirements. And we don't see this fact reflected in the burndown chart ("incremented points by team requirements" stays at 0). Is it normal?

Thanks, and Regards!

[David Barragán]

Hi Enrique,

On Thu, Mar 3, 2016 at 1:44 PM, <enriqu...@beeva.com> wrote:

Hi David,

We are trying taiga.io, and we have some questions related to team vs client requirements:

- In order to clarify, scrum terminology, team requirements are particular cases of user stories, and not other typical Product Backlog Items as Refactoring or Refinement tasks. Is my assumption correct? Can we include within Taiga arbitrary PBI (no uu.ss) in our product backlog?

 

You can use team requirements for refactors if you want, It depends on if you want to see it reflected in the burndown graph or not. We use issues to capture refactors because It doesn't add value to the productl (ex. https://tree.taiga.io/project/taiga/issues?statuses=1,2&orderBy=-created_date&page=1&status=1,2&types=65033); or if we need it to implement a new story, the refector is a task of this story.

- In our last sprint we have tagged some user stories only as team requirements. And we don't see this fact reflected in the burndown chart ("incremented points by team requirements" stays at 0). Is it normal?

No, It could be a bug. 

 - Are you using taiga.io or our a private instance of taiga?  

 - What is you project? (if you are using taiga.io)

 

Thanks, and Regards!

Regards. 

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---

You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/c78397f2-e622-4c93-9bd6-dc81153d020d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Enrique Otero BEEVA]

Hi David,

Thanks for your answer! Our private project in taiga.io is https://tree.taiga.io/project/beeva-carlosmunoz-research-lab/backlog.

We tagged as team requirements several user stories (actually PBIs), because we would like to measure somehow the ratio of delivered business value vs overhead due to refactoring or refining processes. And we wanted to estimate it in user story points.

Anyway, we see "Incremented points by team requirements [...] is 0". Is this a bug?

Regards!
Enrique

[David Barragán]

What is the story with 'team requirements' enabled? I only find 'client requirement' stiories

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/1cb7be97-19fa-4fe7-a1ef-0caac6a619a5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Enrique Otero BEEVA]

'Team requirement' is enabled for https://tree.taiga.io/project/beeva-carlosmunoz-research-lab/us/205 (and also for #207 and #228).

[David Barragán]

Ok, is a bug, the points are reflected only if the story (client or team requirement) is closed.

https://tree.taiga.io/project/taiga/issue/3950

I hope we can solved soon.

Thanks for report.

[Enrique Otero BEEVA]

But our #205 is already closed. And we still can't see the points in the burndown.

[David Barragán]

Yep, according the project stats the sumatorio of team requirements points are wrong and it's not due to its status

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/b96c918a-9d9e-4ce9-a52e-2025f032bd58%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Alejandro Alonso]

Hello Enrique,

We have detected a bug related to team/client requirements when the sprint is the last one. It should be fixed right now in tree.taiga.io.

Thank you very much for reporting and sorry for the inconvenience.

Regards!,

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/CAG7F7Yced%2B4yj5znXYHOfOYMd-41OcPC1%2Bntj6ZF15Pc4DmTkQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--