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

Post a Comment

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
2 comments
Read more

JSON stores and Aggregation for system logs and audit trail. Stop logging with format strings!

This first article explains why you might want to store logs and BI data in a machine readable format. https://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/ The second two get at how you might do that and be able to transition/re-purpose your existing relational stores into a cloud based scalable framework.  http://docs.mongodb.org/ecosystem/tutorial/use-aggregation-framework-with-java-driver/ http://www.bityota.com/3-steps-to-analytics-on-mongodb/ Logging might present a relatively low profile target for schema-less implementation and give you a chance to expose your organization to an important technology for modern web development. With your foot in the door you might convince them to add usage auditing and before you know it you are doing up front analysis on usage in front of your next project.
Post a Comment
Read more

homebrew, git

IN PROGRESS - Steps to contribute a cask to homebrew. Also a good way to stay in touch with git use if you don't have it at work. https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md#getting-set-up-to-contribute 1: Fork the repository in GitHub with the  Fork  button. create or login into your github account use the Fork button at https://github.com/caskroom/homebrew-cask A  fork  is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly,  forks  are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. Now get a 'remote' local copy of the fork you must have git installed comes pre-installed on later osx versions can switch to most current with homebrew - $brew install git $ github_user= ' <my-github-username> ' $ cd " $( brew --repository ) ...
Post a Comment
Read more