TechPostsFromX on Nostr: Scrum's "definition of done" is one of the least agile parts of Scrum. You're done ...
Scrum's "definition of done" is one of the least agile parts of Scrum. You're done when you release. You are doing that every couple of days, aren't you? Of course, the resulting feedback will require adjustments in whatever you thought was done. Attempts to create "done" criteria up front is just waterfall thinking. You won't know if it's right until you get it into your user's/customers' hands.
Source: x.com/allenholub/status/1863083710511218837
Published at
2024-12-01 05:33:56Event JSON
{
"id": "9875da10fc01024f24ecc045bcc58749e94d5ef8633fbf398773384298f977d4",
"pubkey": "52d119f46298a8f7b08183b96d4e7ab54d6df0853303ad4a3c3941020f286129",
"created_at": 1733031236,
"kind": 1,
"tags": [],
"content": "Scrum's \"definition of done\" is one of the least agile parts of Scrum. You're done when you release. You are doing that every couple of days, aren't you? Of course, the resulting feedback will require adjustments in whatever you thought was done. Attempts to create \"done\" criteria up front is just waterfall thinking. You won't know if it's right until you get it into your user's/customers' hands.\nhttps://image.nostr.build/6932aa5d6b3b42091d09e164b93e8f75ad0a82eaa6f089845aefd14691007936.png\n\nSource: x.com/allenholub/status/1863083710511218837",
"sig": "ab39f20624ff0c278649acc5fdad2cd1b8a0961482e626634c9f44d8bf31f088b9d3d98d3a993d7c24e7541da0f0e8ecd18fde65de394d3dab7d448045cc7582"
}
