amauryleclerc / banana Goto Github PK

For instance:
GREEN is very low BV up to RED that means high BV

Need to discuss about this...

Minor enhancements:

• table of absence in "sprint" view has no left margin

Pour faciliter la recherche de stories dans le tableau des stories, il serait intéressant d'ajouter des filtres sur certaines colonnes :

• Name (priorité +++),
• Type (priorité +),
• Add Date (priorité ++),
• Close Date (priorité ++).
  Bonus : Le tri sur les autres colonnes est peut-être moins impactant donc à l'initiative du dev.

show half day in absence table (sprint view and member view)
use half day in capacity calcul

As A PO, I would like to rank the stories in order to display them from the most important to the less important.

As discussed, we can add a "priority" field in link table between story and sprint

To change the priority of a story within a sprint, you can add a "up" and a "down" button on each line of the table.
If the "up" button is pushed, the priority is replaced by the priority of the higher story (flip flap on the priority values)
If the "down" button is pushed, the priority is replaced by the priority of the lower story
If a new story is created, its priority is the priority of the lowest story + 1

e.g:

First state:
STD_1 (priority : 1)
STD_4 (priority : 2)
STD_6 (priority : 3)

After moving the story "STD_4" up:
STD_4 (priority : 1)
STD_1 (priority : 2)
STD_6 (priority : 3)

After moving the story "STD_1" down:
STD_4 (priority : 1)
STD_6 (priority : 2)
STD_1 (priority : 3)

After creating a new story "STD_9":
STD_4 (priority : 1)
STD_6 (priority : 2)
STD_1 (priority : 3)
STD_9 (priority : 4)

The priority value is not displayed in the table (only visible in database)

Sometimes, when someone wants to initiate a sprint, she creates the stories and then the sprint. When we include an existing story to a sprint, we choose the story with a combobox that contains a list of 20 stories (due to ergonomics, it is not possible to include all the exiting stories within this list)
The problem : be able to choose the story in any case...
The same problem is present in the view "stories" where no pagination is present.

Ideas:

1. remove the combobox and replace by a search box: depending on what is entered, a list is filled with proposition found

2. Remove the "add existing story" feature and force the user to create a story within a sprint. If the user wants to create a story in a future sprint but does not know when, we could provide a special sprint called "backlog" ;-) like in Jira...

The story STD_3 is created within the "story" view [OK]
The story STD_3 is not created within the "sprint" view [KO]
Indeed we don't need to create a story alone, but it is always attached to a sprint, even if the sprint is named "backlog PO" for instance...(like in Jira)

As a project manager, I would like to display the burnup graph for the business value done of the current release

With current date, find the release matching the following rule:
release begin date < now < release end date

get the "total BV value" as a stream from the same source

display the ideal burnup series : from (0,0) to (target date, target business value)
display the business value serie from Sprint N to Sprint N+M (Sprint N is the first sprint of the release, Sprint N+M is the last one)

Note:
X axis shows the dates
Y axis shows the business value

e.g: http://timer.onlineclock.net/

use the timer directive: https://siddii.github.io/angular-timer/ ?

As a PO, I would like to have a dark theme for the burndown graph view in order to display this view on a big TV/monitor all day long.

This is a setting that can be set in "Settings view" (checkbox : "Use dark side of the force" ;-))

Add Business value in stories
Add Business value in sprints

As a PO, I would like to see on the burndown graph the stories added during the sprint, and the stories removed (unscopped) from the sprint.

The stickers will take place around the graph point for each date when an event of add or remove took place.

The content of the sticker could be:
"STD_567 Ajoutée (2)
STD_789 Ajoutée (3)
STD_123 Supprimée (5)"

• The number between parenthesis is the number of story points. If this information is not accessible right now, it could be removed from the acceptance criteria.

An example is provided:
http://jsfiddle.net/fm41zbon/

Complexity is mandatory to create the story

As a scrum master
I wish to see the stories related to the project of my choice
In order to have a burndown related only to my project

We can enter a negative value for BV, it's not really possible as BV involve $$$

The modalbox new-story panel will containe a tab view
The first view will show the creation form.
The second will show a list of existing stories to select

application should display text and numbers and dates according to locale set in browser

As a PO I would like to see the avatar of each member to be able to display members boards (we will see later)

In member list view, in first column, we try to get the image from gravatar if member set the option at creation.
If the gravatar is not provided or if the member did not check the option, we could display a standard avatar from a set of provided images (images could be stored in static/ directory).
The member avatar is stored within the member entity

The avatar is displayed in the member view as well (instead of "Use gravatar: true")

As a PO, I would like to have quick action buttons on the story list in order to reduce the number of click

• "Close" action button will allow to set the "close date" to now()

• Change the name in the header "Sprint graph" by a logo
• highlight the view selected in the menu

1. create a sprint
2. add a story
3. go to graph
4. come back to admin
5. sprint number is not set ;-)

As a Project manager, I would like to display the burnup of the current release in order to trigger fixing actions before the end of the release

It involves:
To have a release entity with following data:

• targeted business value e.g: 12000
• target story points e.g: 1000 story points
• start date
• end date

Note that the "release" entity should not be linked to the "sprint" entity at a first glance (may be later on)

This story should focus on creating the release entity with its CRUD Interface

• "+" button opens a popin
• The popin asks for "id", "start date" and "end date"
• list of sprints displayed in a table like the list of stories

When popin opens, It would be nice to have the focus on the first field

For instance :

• when start at noon is checked on the "from date" and the "to date"
• when "from date" > "to date"

Is the button "start sprint" still needed ?
if yes where and what action?

As a PO, I would like to see the link to member view from the sprint view (in the table of absences) when my mouse hovers the name of the member.

Sometimes, some people are taking the plush and keep it a long time before releasing it. It could be a pain for other developers who wait for.

Two ideas:

1. Set a timeout of X minutes (adequate time to be able to merge) : after the timeout, we release automatically the plush. Inconvenient : the developer need to keep an eye on the countdown during the merge. A function like "give me more time" could be interesting in this case. this solution includes the countdown display on the plush page and a button "give me more time" that automatically increases the delay by Y minutes.

2. Ask the developer how many time is required before releasing the plush. A simple label like "I need 22min to make my stuff, please wait until 12h45" : when the delay is reached, the plush is automatically released.

I did not tested this one at the first time, but it is possible to add a story several times in the sprint

As a project manager, I would like to display the burnup graph for the story points done of the current release

With current date, find the release matching the following rule:
release begin date < now < release end date

get the "total complexity value" as a stream from the same source

display the ideal burnup series : from (0,0) to (target date, target story points)
display the story points value serie from Sprint N to Sprint N+M (Sprint N is the first sprint of the release, Sprint N+M is the last one)

Note:
X axis shows the dates
Y axis shows the story points

In order to display the sprint graph on a screen, we should be able to hide the header and sprint choice combo present in the graph view : move the choice combo in the header and add a "hide" header button

The sprint choice does not need to be done in graph view.
It could be moved in menu bar

the reason is to have a graph view without any user interaction

As a PO, I would like to search for stories using date criterias in order to make some reporting about already "done" stories

The goal is to work on stories that have been solved, not to work on stories attached to the current sprint or on future stories

the search criteria should include:

• start date date pickers (choose between begin and end date)
• end date date pickers (choose between begin and end date)

No date is set when the form is displayed.
Only dates that are set are taken into account.

The result is displayed in a paginated table : the first step is to have a "next page" button to get the next page if a next page is found.
a "previous page" button is displayed to get the previous page is a previous page is available.

The sprint "name" should be editable after the creation in order to fix the name if it is not ok

As a developer, I need to build the JAR of the application automatically and to deploy it on a ftp server

URL would be :
ftp://pedrocloud.freeboxos.fr/fr/aleclerc/sprint-graph/2.0.0-SNAPSHOT/

Jenkins use Pipeline script stored within the git repository (build.pipeline)

Sensible information (ftp passwords) should not be stored anywhere within GIT. A settings.xml file will be provided to jenkins maven installation in order to get access to FTP.

FTP would be accessible for humans via basic authentication mechanism.

We could have two more columns to display

• SP
• BV