The call is still out on this approach (I'm guessing it is the new owner Amazon's idea), but I thought it can be a good example of visualization and face to face communication! [..makes stock position obvious to customers, employees, and store leadership.] [Employees can communicate with customers on status of product rather than a tag.]

Calculating Cost of Delay helps Product Owners and business leadership prioritize Product Backlogs. That said, it is not a must-do calculations as there are other ways to prioritize the backlogs which might be more suitable. To help explain it, I transferred

At many of the places I used work at as a traditional project manager (PM), there was almost always a weekly projects status meeting attended by the company executives, directors, managers, and PMs. 

Since 2007 we have seen the advent of several frameworks that claim to scale Scrum or scale Agile such as LeSS, DAD, Nexus, SAFe, DSDM, MAXOS and we will most likely see more to come on scene.

When thinking about the first and third principles behind the Agile Manifesto that state the following:

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software”

One of the most visible aspects of Agile Scrum is the user story card. These cards are present at the center of every Scrum ceremony.  They are in the hands of the Product Owner walking into the first Scrum project team meeting and on the table as the Scrum team reads them and discusses them with the Product Owner in order to estimate the complexity of each story.

Having spent years applying the waterfall methodology, I always had the feeling that it wasn’t right for software development environments, but I just didn’t know what other choices there were. I never felt right with the notion that more templates, more documentation, and more processes on top of the actual work are the answers to every project issue or will guarantee success.

Here are a few recommnded DevOps books.  More to come later..