Versions Compared

Old Version 17

changes.mady.by.user Bianca van der Meer

Saved on

compared with

New Version Current

changes.mady.by.user AJ van Spanje [AgileVisor]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agile is a framework for a way of working in which: 

  • experts are empowered, to take ownership and create high-quality solutions,
  • the gap between IT and Business is bridged, through input and validation by a business-representing Product Owner,
  • transparency, alignment and early escalation (asking for help) are key,
  • short cycles lead to adapting and improving plans,
  • and we experiment with process improvements to gain efficiency.

...

Then <system response>


And remember:


A quick note regarding estimation:

  • We estimate value in the Jira field "business value"
  • We estimate complexity to develop in the Jira field "story points"

These estimations use a simplified Fibonacci range (0, 1, 2, 3, 5, 8, 13, 20, 40, 100).

The reason for this is that people are much better at estimating small numbers.

There is no real difference between a "48" and "49", because any estimate that large will include a large portion of uncertaintly. 

For this reason work with large estimates is broken down into smaller, workable pieces (that we can still test to validate a piece), and re-estimated.

A recommended tool/game for estimating together with a group is: https://planningpokeronline.com/

Sprinting or Continuous Flow

...

Two things are important in this:

  1. We should use the naming convention when creating a new fix version/s.
  2. We should release a fix version/s in Jira after the deployment is successful.

...

Using the tool Jira consistently, means that we obtain transparency of our process and progress. This allows our team to Inspect how we are doing, and Adapt in order to gain higher efficiency, and grow together.Reports


Each team board contains standard reports. 

  • these are only as good as the data we put in
  • for Scrum the Burndown Chart and Sprint Report are useful
  • for Kanban the Cumulative Flow Diagram is useful

for higher level planning the Epic and Version report are useful, but we will need to grow into these reports yet at YME.


A Burndown Chart shows the progress during a sprint. The more the red line follows the grey line, the better:

A Sprint Report shows the results after a sprint. The fewer items have a * or are removed from sprint, the better:

A Cumulative Flow Diagram shows how WIP is limited and progress is made in Kanban. The slimmer the colored line between backlog/resolved, the better:

...