Showing posts from April, 2015

Kanban Metrics: Learning to See and Improve

Kanban is a tool, it`s a culture and mindsets change tool, it`s a approach to change management. In order to make that happens we need to learn to see waste and see bottlenecks. There are several things you can do to archive that like retrospectives and peer-reviews but you also should be considering do as much metrics as you can. It could sound awkward talk about metrics on a Lean/Agile context because could easily sounding like non-sense but its not. So what kind of metric should i have, well that will depend of your system, when i say system i do not mean software but your people work system. Metrics does not need be atomic and microsecond precise you should see metrics as a thermometer rather than a raw number,

Lean, Deming a the new Culture

Every company has motivations, as someone may say make money, others companies now a days think a lot about the Golden and Circle and the WHY , the arise of the PURPOSE MODE and make something that is good for the world and later make money. I learned a great deal from Deming ideas and principles. This man was one of the best Gurus we ever had into the world. He was a Humanist and belive into very simple ideas like: People are Good, People want do great work and have proud on they jobs.  50 years ago the WASTE was around Manufacturing industry. That`s why deming work was around japan and us, around Toyota and other great companies.  IF Deming was here with us today most likely he would be working with IT because today this is where the WASTE lies. I found that funny because IT changes so fast and we still dont know how to deal with changes and cultural and behaviors changes.

Scrumban Experiences

Back into 2008 i was doing lots of scrum like everybody else. I spot several issues working purely with scrum like: Issues working with delivery dates, issues working with distributed work, or work beyond the team level, issues working with FAKE Pos, or pos who could not make any call or was really afraid to make calls because a specific corporate culture. In brazil CMMI and process, unfortunately are still strong, maybe there are not strong in a direct way but they are still into a indirect way.  People often go to new methods and practices but with old culture and that does not work because as Deming said once: Dont copy the tools copy the principles in order to get the principles it require to change culture and values, for brazil old values around process and quality.

Micro-Workers: A flavor or Microservices?

Microservices are about ISOLATION . I need point out some different aspects here, keep in mind the word: Microservices is compose by 2 words, micro, thats where you got the isolation, minimal business unit, great marriage with REST in sense of RESOURCE and several other things i mention on previous post. There is another word call: service. This is where SOA come to play, there is lots of people talking BAD about SOA now a days, but they dont realize MSA is SOA.  Service is not a web service, so that word has more meaningful than people imagine. SOA is about principles , its about great foundations that enable Service Orientation. That`s is an Architecture but its also a way to think also called SO(Service Oriented). Microservices make a lot of sense if you are coming down from a monolith its very DDD like if you pay attention.

DevOps Economics

Everybody is talking about DevOps now, which is good, but honestly DevOps is way bigger than what people are talking about. One of the CORE roots of devops is AUTOMATION of infrastructure - automate everything, that's true and that is so important, but that is not the only thing. DevOps is not a framework, is not a model, is not a process - DevOps are some experiences from folks around the globe who have had success in extending agile to new frontiers like operations - some people started a movement called Agile Operations which I think is great. DevOps is in some sense the evolution of the cultural change that agile and Lean promoted in development from the early 2000s. Now is the time to break more silos and continue to improve things. It's not easy, changing culture, but it is a necessary step for the evolution of software development.