A quick intro to SCRUM and KANBAN By John Voris

Because we work on a Monthly Cycle in SCRUM, we can change the Backlog, and we can change the SCOPE of a project and the Priorities and Requirements are allowed to change.

I want to stress Information Radiator ( Big Status Board ) with Swim Lanes to show: Backlog Items Work In Process shows status and movement Collection of Items Tested and Done-Done It is a Manual process that is easy to change Activities in a Sprint: Backlog Refinement / Estimates Devs Pull their next Task A Daily Standup Meeting to see blockages A Retrospective to see how the Sprint went Tying all these together is Definition of Done for the Tasks of the Team

In the Retrospective, we look for wastes in our flow Definition of DONE stops OverProcessing & Over Production

which emphasizes the People side of Project Management Often mentioned is The Agile Manifesto which emphasizes the People side of Project Management Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Agile was the term chosen since LIGHTWEIGHT Project Management would be hard to sell to management

We use Test-Driven Development . . . Cylcing through Red Green Refactor to enforce quality. When we cut corners, we accumulate Technical Debt.