Teams can use the cumulative flow diagrams to understand how work progresses, identify bottlenecks, and determine the appropriate pace of work.
Posts tagged management
Blockers in agile and kanban
An impediment, also known as a blocker, is an obstacle preventing team members from completing tasks or achieving sprint goals. Various types of blockers need to be addressed immediately to maintain a smooth workflow
Cycle time and lead time
To improve cycle time, focus on streamlining your actual work processes. For lead time improvements, look at reducing delays between stages.
Service classes
The principle of service classes, a key component of Lean methodology, is instrumental in efficiently organising, prioritising, and managing work.
The seven wastes
Taichi Ohno identified seven types of waste that do not add value to the customer. The wastes were categorised to assist employees in systematically identifying and eliminating them.
Minimum viable teams
The power of minimum viable teams lies in their streamlined communication channels. With fewer members, information flows naturally and decisions happen swiftly.
Self-organising teams
Self-organising teams are groups that work together toward a common goal, making decisions and managing tasks without supervision or authority from an outside source.
Scales Agile Framework (SAFe)
SAFe, or scaled agile framework, was developed by Dean Leffingwell and Drew Jemilo to address a businesses’ evolving needs. When it was created, software development teams were largely reliant on traditional project management techniques. SAFe was developed in response to organizations’ increasing need to adapt rapidly to market changes while still maintaining high quality. Today, it is one of the most popular agile development approaches. SAFe is…
Feature-driven development
Coding standards, measurement audits, and metrics are crucial to F.D.D.’s quality concept. Feature-driven development prioritises meetings compared to other methodologies (such as Scrum and XP).
Sprint goal
Sprint planning marks the beginning of each sprint or iteration of work. This meeting is designed to align the team on the tasks to be completed during the upcoming sprint and ensure that everyone understands the objectives and scope of the work.