agile

/agile
13 02, 2018

DevOps, Organizational Change or Organizational Transition? It’s both and that’s why so many fail!

By | 2018-02-13T09:26:58+00:00 February 13th, 2018|agile, best practices, DevOps, testing|Comments Off on DevOps, Organizational Change or Organizational Transition? It’s both and that’s why so many fail!

Unfortunately, the DevOps movement is marked by the vast majority of organizations failing in their attempts at DevOps. Gartner points out that 90% of organizations who fail to first deal with their cultural issues fail in their DevOps attempts. The way this is worded is a little misleading, because it gives the sense that there is some small portion of organizations who are failing to deal with culture and the majority have successfully dealt with their cultural issues. It’s actually the opposite, the vast majority of organizations fit into the category of failing to deal with their cultural issues and will most likely fall into the 90% failure category. So, the question is, why is it so difficult for organizations to deal with their cultural [...]

5 02, 2018

Is Management by Objectives (MBO) silently sabotaging your DevOps efforts?

By | 2018-02-14T08:58:20+00:00 February 5th, 2018|agile, best practices, DevOps|Comments Off on Is Management by Objectives (MBO) silently sabotaging your DevOps efforts?

Excerpt from A Tale of Two Companies The vast majority of DevOps practitioners and advocates have repeatedly mentioned that DevOps uses the work of Dr. W. Edwards Deming, what they all fail to mention is that Dr. Deming was a fierce opponent of Management by Objectives (MBO) which to this day is still ingrained in the culture of many organizations and works counter to what the DevOps movement is attempting to accomplish. Management by objectives was first popularized by Peter Drucker the most revered guru of American management in his 1954 book The Practice of Management. Management by objectives is the process of defining specific objectives within an organization that management can convey to organization members, then deciding on how to achieve each objective in [...]

20 01, 2018

Release of A Tale of Two Companies

By | 2018-01-20T10:42:06+00:00 January 20th, 2018|agile, best practices, DevOps, kanban, SAFe, scrum, testing, XP|Comments Off on Release of A Tale of Two Companies

A Tale of Two Companies is a narrative story about two companies who are facing competition from new entrants into their business vertical and are looking to regain their competitiveness through Agile/DevOps. Along with the story of the two companies, there are learning points in each section. This book takes a very different tact then the majority of DevOps books on the market, the book attempts to explain in simple terms through Learning Points why, as Gartner has pointed out, 90% (the true number is probably higher) of the companies attempting DevOps are failing. A couple of sample Learning Points the book covers are below: Many in the industry have probably heard the reference to the “Blame Game”, which is the conflict between development and [...]

14 03, 2017

Value Proposition Cards

By | 2017-03-14T15:32:49+00:00 March 14th, 2017|agile, best practices, DevOps, kanban, SAFe, scrum, XP|Comments Off on Value Proposition Cards

A common problem in the world of software development is bringing Technical Debt to the forefront so that organizations can clearly see why they need to make the move towards Agile and DevOps. The issue is, how do we get everyone in the organization on board? Even when you explain to the business side that research has shown that organizations of all types and sizes are having to spend 70% to 80% of their entire Software Development budget simply maintaining existing code, they don’t believe this includes them or they simply don’t fully understand the issue. The problem is that they see the requests they make to Software Development moving through the Software Development process and believe this is all new work being created for [...]

6 12, 2016

Explaining Adjustments Costs in DevOps

By | 2016-12-06T10:53:20+00:00 December 6th, 2016|agile, DevOps, Uncategorized|Comments Off on Explaining Adjustments Costs in DevOps

Coaching a DevOps implementation is a challenging proposition for a number of reasons. One of these reasons is not only getting the business side to buy in, but to keep them on board throughout the entire journey. The truth is that many organizations, vendors and coaches/consultants don’t fully appreciate just how steep the mountain is that must be climbed in order to bring about the culture change required to successfully implementing DevOps. The implementation of DevOps will need to account for the ‘adjustment’ issues that almost always occur when making any organizational change. By adjustment issues we mean the loss in performance that could be incurred before DevOps is fully implemented and functioning as intended. But estimating the nature and extent of any implementation issues [...]

15 11, 2016

Hidden Constraints/Process Improvements in Value Stream Mapping and Theory of Constraints

By | 2016-11-15T13:14:55+00:00 November 15th, 2016|agile, best practices, DevOps, kanban, SAFe, scrum, testing, XP|Comments Off on Hidden Constraints/Process Improvements in Value Stream Mapping and Theory of Constraints

One of the starting points with any organization looking to start the DevOps journey or even just looking for process improvement is to create a current and future state Value Stream Map or apply the Theory of Constraints. The concept of Value Stream Mapping has been around for many years (possibly as early as 1918) and is usually associated with Lean. Value Stream Mapping can be used in conjunction with the Theory of Constraints or they may both be applied separately. Value Stream Mapping helps show how both materials and information flow as a product or service through the process value stream, helping teams visualize where improvements might be made in both flows. The Theory of Constraints is used to concentrate on reducing the throughput [...]

26 10, 2016

QA, DevOps is an Opportunity not a Threat

By | 2016-11-15T13:10:47+00:00 October 26th, 2016|agile, DevOps, testing, Uncategorized|Comments Off on QA, DevOps is an Opportunity not a Threat

If you look around most QA message boards you still see the topic of automated testing versus manual testing being debated over and over. I am not going to get into this debate because I believe the overwhelming evidence, industry direction and true nature of what quality assurance is supposed to be dictates that we should be moving to automated testing. What I am going to discuss is my belief that DevOps actually presents a great opportunity to those in QA who can see the underlying foundation of what DevOps is. DevOps borrows from the quality principles of Deming, TQM and Lean, with the emphasis being on preventing issues instead of detecting them. In other words, doing quality assurance instead of quality control. So how [...]

11 10, 2016

Get a Good ‘Work-Out’ in DevOps

By | 2016-10-11T13:29:27+00:00 October 11th, 2016|agile, best practices, DevOps, Uncategorized|Comments Off on Get a Good ‘Work-Out’ in DevOps

The idea of including everyone in the process of improvement is one of the key principles of TQM, Lean and now DevOps. There are numerous ways being suggested in DevOps articles, blogs and books to involve everyone and create a continuous improvement culture. I suggest that instead of trying to re-invent the wheel, many of these organizations should consider tried and tested approaches, such as the ‘Work-Out’ approach that originated at General Electric. This approach allegedly was developed by Jack Welch, the then CEO of GE. The reasoning behind developing this approach was the recognition that employees are an important source of new and creative ideas, and an instrument for creating an environment that pushes towards a relentless, endless companywide search for better ways to [...]

1 07, 2016

Incorporating Andon Cord in DevOps

By | 2016-07-01T16:39:18+00:00 July 1st, 2016|agile, DevOps|Comments Off on Incorporating Andon Cord in DevOps

Andon Cord is a Lean manufacturing principle and tool used to notify management, maintenance, and other workers of a quality or process problem. The concept revolves around a device incorporating signal lights to indicate which assembly line workstation has a problem. Normally alerts are activated manually by a worker using a pull cord (Andon cord) or button, or may be activated automatically by the production equipment itself. The system may include a means to stop production so the issue can be corrected. The Andon System was developed as one of the principal elements of the Jikoda quality method pioneered by Toyota as part of the Toyota Production System (TPS) and has become part of the lean manufacturing approach. Andon cord gives the worker the ability, [...]

31 03, 2016

DevOps and the Theory of Constraints

By | 2016-03-31T12:04:46+00:00 March 31st, 2016|agile, best practices, continuous integration, DevOps, kanban, Uncategorized|Comments Off on DevOps and the Theory of Constraints

As the DevOps movement has started to take hold in the software development industry, one of the great benefits of this is that individuals are starting to become aware of tried and true Lean Manufacturing and TQM practices. Having received an undergrad degree in Operations and having worked for the first three years of my career for a Lean Manufacturing shop, I have always been sort of puzzled how software development never seemed to have any industry wide concrete foundational practices that companies followed in order to improve quality and reduce cycle time. A while back I read a DevOps article where someone was talking about adopting Lean Manufacturing concepts for software development and they specifically mentioned one of the foundational concepts all Lean Manufacturers [...]

X