Skip to main content

Posts

Showing posts from September, 2017

Is today's world all about creativity and ideation?

Are they the seeds to be nurtured to bring in automation, innovation and transformation.  There is a saying, necessity is the mother of invention. I would say, innovation is amalgamation of creativity and necessity.  We need to understand the ecosystem, to apply creativity and identify the ideas to bring in change. We need to be competent with changing ecosystem and think beyond the possible. What is the biggest challenge in doing this? "Unlearning and Learning", we think the current ecosystem is the best. Be it health, finserve, agriculture or mechanical domain, we need to emphasize with the stakeholders, to come up with the strategy to drive. The very evident example here is the quality of life is changing every millisecond. Few decades back the phone connection was limited to few, but today all the millennials are having a mobile phone. Now phone is not just a medium to talk, but are so powerful devices that an innovative solution can be developed on it.

“OUTCOME” or “OUTPUT” driven Agile

Hello All,     Nowadays IT industry is bombarded with articles on Agile with loud and clear message #BeLean. Everyone around teaches AGILE as in #GOAGILE, #BEAGILE, #AGILITYLEADS and many more hashtags around #ONLYAGILE. Lean Engineering gurus have been coaching corporates to go #AGILE and be #LEAN. Literal English meaning of being Agile is to be nimble, to be able to adapt to the changing needs of company to achieve goals as to what is desired by business. But why do we need Agility, is it to be able to achieve outcome i.e., #BusinessesNeed with speed i.e., #Velocity? I am perplexed with what I keep hearing around Agile practices and I firmly believe we should try to understand the rational for being Agile by choosing right “O”, either go #Outcome or #Output. What will you prefer without reading this blog, Output or Outcome?   Let me take you two decades back when there was a need for transformation. Transformation from big-bang i.e., #waterfall to iterative i.e., #lea

Code Branch and Merge strategies

Learn Git in a Month of Lunches Hello Everyone, IT industry is going through a disruptive evolution where being AGILE and adopting DevOps is the key catalytic agent for accelerating the floor for success. As explained in my earlier blog, they complement each other rather than competing against one another. If Leaders will at the crossroad where in case they need to pick one what should be their pick. There is no right or wrong approaching, it depends on the scenario and dynamics for the program or project. I would personally pick #DevOps over Agile as its supremacy lies in ACCELERATING delivery with RELIABILITY and CONSISTENCY . This path will enable and empower development teams to be more productive and prone to less rework. Does this mean adopting DevOps with any standard will help reap benefits? In this blog, I will focus on importance of one of the standard and best practice around Code branching and merging strategy to get the desired outcome by adopting DevOps. To

“Agile and DevOps” OR “Agile or DevOps”, Why?

Hello All,   Buzzwords for 2017 are “ Go Agile ” and “ Adopt DevOps ”, but for 2018 no surprise if corporate leaders call it “ Practice Agile Ops ” or “ Practice Agile Dev Ops ”. Biggest puzzle corporate decision makers are trying to solve is “Can an organization be Agile without Adopting DevOps?” or “Can DevOps be adopted without going Agile?”. There are quite a few books which are published on the same topic. Good to have these reads for individual library: True Agility from Agile+devops: Assuring Data Governance and Boosting Agility Leading the Transformation: Applying Agile and DevOps Principles at Scale High Velocity Itsm: Agile It Service Management for Rapid Change in a World of Devops, Lean It and Cloud Computing Agile Application Lifecycle Management: Using DevOps to Drive Process Improvement   Let us go back to 90’s and try to understand the journey of this change and need for this transformation. During early days of development when most of the soft

Tips for effective Agile Retrospective Ceremony

Hello All,   Welcome back in this blog I will cover one of the key ceremony for Agile framework. In my last blog I wrote "how we can avoid Agile estimation errors" by adopting various estimation techniques. What is not important for us is to be 100% accurate in estimation in the first attempt ( Agile is an A rt of G rooming using I ntelligent L ean E ngineering) but key point there is to embrace the right intent and the outcome. Over last decade, Agile practices had matured and is one of the most adopted and accepted framework across industries. Industries are going through a Disruptive Evolution phase where Agility is the key to success, irrespective of domain.     There are certain questions on should try to answer: Does sprint retrospective a single man show, by so called “SCRUM MASTER” or “TEAM LEAD” or “PROEJCT MANAGER”? Does sprint retrospective ceremony add any value to the team? How frequently should we have sprint retrospective ceremony? D