Giter Site home page Giter Site logo

scrum-accountabilities's People

Contributors

rosannevanderlinden avatar sjoerdly avatar ziryan-salayi avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

scrum-accountabilities's Issues

Reword cards to better reflect the meaning of the card and makes sure it fits only one accountability. #2

During last training we found a couple of cards for Version 2.3 that might need rewording:

Card 2: Foster an environment where work is ordered into a Product Backlog.
Explanation: This card confuses people but is literally in the Scrum Guide. The confusion maybe comes from the summary being split.
Suggested update: Fosters an environment where the work for a complex problem is ordered into a Product Backlog (this copies literally from the Scrum Guide)

Reword cards to better reflect the meaning of the card and makes sure it fits only one accountability. #1

During last training we found a couple of cards for Version 2.3 that might need rewording:

Card 1: Support application of focus for creating a Done Increment.
Explanation: This card confuses people by the word 'application' which tends to be a Dutchism.

Suggested update: Supports and makes sure there is focus towards creating a Done increment/Establishing an environment where people can focus on creating a Done increment. <-- This option might be too long on the cards. In that case go for suggested update 2.

Suggested update 2: The word application might also be replaced by utilization: Supports utilization of focus for creating a Done Increment.

Card: Committed to creating any aspect of a usable increment; should be under Developers not Scrum Team

In the Mural template this card is currently under Scrum team in the Solution. This is incorrect as this is the literal first sentence at the Developers accountability in the SG 2020.

image

I've created a Mural with this correction applied. If approved this needs to replace the previous template.
https://app.mural.co/t/scrumfacilitators4035/m/scrumfacilitators4035/1668433089983/7cff34bae46fb73227c601f70b751564d64df546?sender=scrum4good8091

Card: Managing interactions toward scrum team cannot be related to the guide anymore - suggest rewording

The Card
"Managing the interactions towards the Scrum Team"
seems like pre-2020 wording.

Current candidates in the guide:
"Facilitating stakeholder collaboration as requested or needed"
"Removing barriers between stakeholders and Scrum Teams" (which is essentially the same, but feels opposed to the current card)
and to lesser extent
"Helping employees and stakeholders understand and enact an empirical approach for complex work"

I suggest updating the card to the first sentence:
"Facilitating stakeholder collaboration as requested or needed"
As I feel this covers both other possibilities.

Input welcome!

Specify type of Burndown Chart

There is one card called "Updating the Burndown Chart"

To know if it is a Sprint-, Release Burndown or maybe even something different would help to move the card in the right quadrant.

Create dutch translation

SF operate a lot in dutch companies. Some of those are dutch language focused (and have many employees not well versed in english).

It may add value to have a card set with dutch translations added to the back. Or a fully dutch card set.

Translations should be checked with the translated dutch Scrum Guide found on scrumguides.org

Add source files to github

These are currently indesign files. Should be ported to ppt for easier collaboration and development with all involved?

potential improvement in Scrum Team?

From the website chat:

Hi, I am checking the Scrum Accountabilities. The Scrum team is Accountable but the developers are committed to creating a valuable, useful increment every Sprint. Could be a fault, Scrum team orange should be: Accountable for creating a valuable, useful increment every Sprint. It is just one word ๐Ÿ˜„ gr Erwin Lepp
It is on the result

non-SG-related cards - mark subtly to easily keep them out of your facilitation

Maybe we should have a discussion on the 'non-framework' cards. The cards not relatable to Scrum Guide 2020.

Essentially there are a bunch of cards, including ROI, holiday approval and the burndown one, that are not defined from a Scrum perspective. They have a 'matching' spot mostly, but not as clear cut as the other cards which are directly relatable to the SG2020 https://scrumguides.org/scrum-guide.html

It may be nice to keep these separated, maybe mark them with a small dot for the facilitator. I would like to be able to keep them out and add them later for a more general discussion and keep the initial sorting and learning 'clean'.

Relates to #2 as that is one of the Non-SG cards

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.