Giter VIP home page Giter VIP logo

Comments (2)

Hnasar avatar Hnasar commented on July 17, 2024 3

This can also be addressed by changing the template like:

<!-- This is an optional element. Feel free to remove. -->
-### Positive Consequences
-
-* {e.g., improvement of one or more desired qualities, …}
-* …
-
-<!-- This is an optional element. Feel free to remove. -->
-### Negative Consequences
+### Consequences

-* {e.g., compromising one or more desired qualities, …}
+* Good, because {e.g., one or more desired qualities, …}
+* Neutral, because {e.g., one or more desired qualities, …}
* …

from madr.

koppor avatar koppor commented on July 17, 2024

Let's have a try for a longer list of "Options".

Markdown

<!-- This is an optional element. Feel free to remove. -->
## Pros and Cons of the Options

### {title of option 1}

<!-- This is an optional element. Feel free to remove. -->
{example | description | pointer to more information | …}

#### Pros

* {argument a}
* {argument b}

#### Neutral

* {argument c}

#### Cons

* {argument d}

Example

(based on https://github.com/adr/madr/blob/main/docs/decisions/0015-include-consulting-informed-of-raci.md)

Pros and Cons of the Options

Include "Consulted" and "Informed" of RACI

Pros

  • These two roles of RACI are well understood.
  • We make these fields optional, thus it keeps MADR still lightweight.

Cons

  • It adds two additional fields

Include all fields of RACI

This would add "Responsible", "Accountable", "Consulted", and "Informed"

Pros

  • Complete RACI would be included

Cons

  • Get confused about who is "accountable" and who is "responsible".
  • If decisions are mostly taken by consensus in small committees, then there might not be an "accountable" person.

Thoughts

I think, this is really lengthy. Not sure if MADR can still be called "lightweight" then.

Maybe, it is a tooling issue?

  • In case MADR stays as is, a tool could allow with drag'n'drop to put arguments of options to consequences and reformat them accordingly
  • In case MADR is modified, a tool could render MADR in a "leightweight" form

Other options

Using "Positive, because" and "Negative, because"

  • Bad, because this does not list real consequences, but is just a synonym for "good" and "bad"

Remove "Positive Consequences" and "Negative Consequences"

They don't seem to be used much in the wild, thus why not just removing them and leaving it open to everyone?

from madr.

Related Issues (20)

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.