Skip to main content

Clifford Berg

Clifford Berg
Profile picture for user cliffbdf

Member for

4 years 8 months

Agile and DevOps transformation consultant who has helped with more than ten transformations; author of four books, founder and editorial chair of Transition2Agile (http://www.transition2agile.com). During the mid-1990s, Cliff co-founded Digital Focus, a successful IT startup. Primary contributor to multiple open source projects.

Company
Agile Arts
Job Function
Consulting
Job Title
Principal
Industry
Agile transformation consulting
Interests
Agile
DevOps
Leadership
Lean
Project Management
Quality Assurance
Security
Test Automation
Country
United States
Profile picture for user cliffbdf
Clifford Berg

An accomplished system architect with experience in "devops", security, and software architecture, Clifford Berg is the founder and editorial board chair of Transition2Agile (http://www.transition2agile.com). He is an IT agile transformation management consultant, facilitator, speaker, management “coach”, and author of four books. During the mid-1990s, Clifford co-founded Digital Focus, a successful IT startup.

All Articles by Clifford Berg

All Stories by Clifford Berg

Four yellow pipes Continuous Delivery Is Not a PipelinePretty much everything you hear about DevOps mentions “the pipeline.” Continuous delivery is not really about the pipeline, however. Continuous delivery is about two things: testing strategy and branching strategy. The pipeline is important; it is an integral part of DevOps. However, the central element is the practice of testing continually using automated tests.
Don't Shoot Agile in the Foot How to Plan and Execute Programs without Shooting Agile in the Foot

Program planners in IT organizations have a dilemma: On one hand, their agile teams tell them that if requirements are defined up front, agile teams cannot operate; but on the other hand, the program’s budget and scope need to be defined so that resources can be allocated and contracts can be written for the work. How does one reconcile these conflicting demands?
DevOps off the Rails Has DevOps Gone Off the Rails?

DevOps is evolving with some potentially very harmful choices embedded in it. Among these are poor adoption of sound computer science, little thought to the maintainability of DevOps code, and choices of tools based solely on productivity without concern for maintainability. Will this cause DevOps to fail to live up to its potential?