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.
The seven wastes
Browsing Category Agile
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.
Sprint velocity
Various models, techniques, and tools can assist with effort estimation in software project management. An agile software project involves iterative development, in which customer feedback informs future iterations. This means estimations and planning need to be updated over time. Scrum teams use three levels of planning to accomplish this: release planning, sprint planning, and daily planning. Software development based on agile principles has adopted scrum widely due…
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…
Technical debt in software development
According to industry observations, design trade-offs result in the most significant technical debt, which code quality measurements cannot detect. Assessing technical debt in industry and research is difficult due to the lack of practical tools.
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).
Disciplined agile delivery
According to the Disciplined Agile Process (D.A.D.), stakeholders recognize that external customers are not always the project’s focus. The term “customer” has become popular among some software teams because it has shifted their focus from technology to business needs.
Clean code in software development
Writing code that’s easy to read and understand is essential to ensuring clean code. This enables others to comprehend its purpose at a glance.
The burndown chart
Scrum teams generally use the burndown chart to communicate and track their overall progress throughout the Release lifetime. It is a must-have tool, especially for Scrum teams, to quickly monitor the product’s overall scope while maintaining a schedule for their release progress. Furthermore, it helps teams compare the planned work versus the obtained work in a measurable way. A burndown chart of any kind usually helps…