Tuesday, March 26, 2019
Tuesday, March 19, 2019
Monday, March 18, 2019
Scrum and Kanban Summary
- Split your organization into small, cross functional, self organizing teams.
- Split your work into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item.
- Split time into short fixed-length iterations (1-4 weeks) with potentially shippable code demonstrated after each iteration.
- Optimize the release plan and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration.
- Optimize the process by having a retro after each iteration.
- Visualize the workflow.
- Split the work into pieces, write each item on a card and put them on a wall.
- Use named columns to illustrate where each item is in the workflow.
- Limit WIP. Assign explicit limits to how many items may be in progress at each workflow state.
- Measure lead time -- average time to complete one item, sometimes called cycle time. Optimize the process to make lead time as small and predictable as possible.
Scrum vs. Kanban
Thursday, March 14, 2019
Far too many times, I have come across organizations that hire Agile Coaches, Enterprise Coaches and Agile Consultants as Change Agents for Enterprise Agile Transformation. These people work closely with the teams on ground as well as the senior management, and leadership. However, the most fundamental unit of Change at the ground is the Scrum Master, who for reasons unknown are quite too often left out of this change as someone expendable, and ignored, and thus end up not knowing the management strategy, nor are they part of any of the change initiatives. This impacts the organization at large, in that the change is essentially comes to mean as a top down thrust where the rudimentary / elementary units aren't engaged to meet the organizational objective.