Agile teams and their organizations do not go faster by increasing velocity. They go faster by deploying increments into production more frequently to minimize depreciation and the cost of delay.

Once in one of my projects, I met with the full development team so I could get their thoughts on adopting a continuous delivery pipeline before we made anything final. I saw all the benefits, but I was cautious by nature, so I kept asking WHY and What can We do, What the challenges were; What were the barriers to entry?

A continuous delivery pipeline has many benefits for the team, business, and the users:

1. Ensures that most major issues and conflicts are identified early in the development process when it is cheaper to fix these.  

2. Less stress during deployments and releases - happier developers!

3. Increased predictability in workflow since the process is iterative.

4. Transparency: everyone is aware of all the needed steps and all or portions of the pipeline can be managed by anyone in the team.  

5. When a step in the pipeline becomes obsolete or a modification is needed, the team can implement changes easily or rollback if needed.  

6. Allows the team to collect peer, business, and user feedback more rapidly.

7. Cleaner code and stable environments, lower risks with deployments

8. Increased ability to react to market and user needs, nimble workforce.

“Shop for Him /Her This Valentine’s Day!”

Kanban means (signboard or billboard) and is a card that "contains information that serves as a work order". "...gives information concerning what to produce, when to produce, in what quantity, by what means and how to transport it". Source: See image.

Kanban has 6 rules:

1. Do not send defective products to the subsequent process. (QA!?)

2. The subsequent process comes to withdraw. (Pull)

3. Produce only the quantity withdrawn. (Lean)

4. Equalize the production. (Heijunka)

5. Kanban is a means for fine-tuning. (Kaizen)

6. Stabilize and rationalize the process. (Standard Work)

Daily Scrum: The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal, and adapt and replan the Sprint Backlog as necessary. What has changed in the 2020 Scrum Guide is the method. Gone are the three questions listed in previous guides, replaced with this less prescriptive description: 

“The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This creates focus and improves self-management.”