cards42.org

Cards for Analyzing and Reflecting on Doomed Software
A cards with an arrow on the y-axis on the left side named
Download: PNG PDF SVG

“Let’s add this new framework that was launched last week!”

I’m sure in one of your projects you have heard this statement in a similar form before or even made it yourself. First and foremost, you develop your software for your users. And yet, far too little attention is paid to this when making decisions, what benefits your target group has from the upcoming change.

You want to write your own complex logging framework for your software and estimates a development time of about six weeks?This will most likely have no noticeable impact on stakeholders, but simultaneously prevents you from developing new features during this time.

You plan to integrate another new payment method into your system, but aren’t you sure if nine weeks of development time can be spent on this? Many of your users might be grateful to have a new opportunity. This will most likely have no noticeable impact on stakeholders, but simultaneously prevents you from developing new features during this time.

You plan to integrate another new payment method into your system, but aren’t you sure if nine weeks of development time can be spent on this? Many of your users might be grateful to have a new option to pay for products. So this feature has a very big benefit.

With this card you, can check your next decisions regarding how much benefit users get from the changes and whether your discussions actually are useful.

More information