Skip to main content
There’s a lot of talk about transformation and some metrics around what we are lacking and need to do better. Do we also know what we do well and the good things about our work processes and environment that we want to keep? I’m concerned that if we don’t diagram this as a spectrum we risk running over those good things that we do in the course of transforming.

Running agile retrospectives at team levels could provide us with this feedback


DAKI – drop, add, keep, improve | Fun Retrospectives

DAKI is a great data gathering to foster the thinking around practices and the value the team get from it. It helps team members to understand each other ...

KALM – Keep, Add, More, Less | Fun Retrospectives

Activities and ideas for making agile retrospectives more engaging ... KALM (Keep, Add, More, less) is a retrospective activity that fosters the conversation to the ... Keep – something the team is doing well and you recognize the value on it.

5 Tips to Keep Getting Value from Agile Retrospectives - Ben Linders

Jan 21, 2016 - People often ask me what to do to prevent that teams get bored when doing agile retrospectives for a longer period. The short answer is: Make ...

Comments

Popular posts from this blog

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services

Dockercon 2021

 Dockercon 2021 Replay presentations ex:  https://docker.events.cube365.net/dockercon-live/2021/content/Videos/zo9AAafDLCPRv2rom https://github.com/docker/roadmap/issues/201 https://aws.amazon.com/ecs/anywhere/ https://cloud.netapp.com/blog/aws-cvo-blg-amazon-eks-anywhere-and-ecs-anywhere-multicloud-services https://docs.docker.com/cloud/ecs-integration/ https://github.com/GoogleContainerTools/skaffold https://docs.docker.com/compose/profiles/ https://docs.docker.com/compose/compose-file/compose-file-v2/ Lessons Learned With Dockerfiles and Docker Builds https://docs.docker.com/develop/develop-images/build_enhancements/  &  https://docs.docker.com/buildx/working-with-buildx/ "Java 11 is first version that is fully 'container aware'." As in it respects cgroups.  Docker Playground https://labs.play-with-docker.com/ Compiling to Containers with BuildKit https://github.com/agbell/compiling-containers https://earthly.dev/

Build software like you build houses

Interfaces facilitate visibility. Software is the only engineering practice that doesn't allow runtime visibility to end-user. If this were true for construction, it would mean your builder would have to live with you for you to even guess what the problem is. https://vimeo.com/221049715 https://github.com/stripe/veneur