7 Wastes in SW Development

A Complete Guide to eliminating wastes in software development environments.

Ratings 4.17 / 5.00
7 Wastes in SW Development

What You Will Learn!

  • Technical Aspect for Software Development Mindset
  • How to deal with the 7 Wastes in Software Development

Description

SW Development Mindset: 7 Wastes in Software Development is a Complete Guide to Software Development Heads, Managers, Team Managers and Team Leaders  to eliminating wastes in software development environments.

  1. Partially Done Work: This waste refers to work that has been started but not completed. Incomplete work can lead to confusion, rework, and reduced productivity. It's essential to finish tasks and user stories before moving on to new ones.

  2. Extra Features: Extra features, often referred to as "gold plating," are functionalities or enhancements that provide little to no value to the end-user. These can add complexity, increase development time, and distract from more critical tasks. Focus on delivering what the customer needs.

  3. Relearning: Relearning waste occurs when developers or teams repeatedly rediscover knowledge or reinvent solutions that already exist within the organization. Proper documentation, knowledge sharing, and a culture of learning can help reduce this waste.

  4. Handoffs: Handoffs between different teams or individuals in the software development process can lead to delays, miscommunication, and errors. Minimizing handoffs and encouraging cross-functional teams can help mitigate this waste.

  5. Task Switching: Task switching, or context switching, occurs when developers are forced to switch between multiple tasks or projects frequently. This can lead to reduced productivity and increased errors. Implementing a work-in-progress (WIP) limit and minimizing multitasking can help address this waste.

  6. Delays: Delays in the software development process can result from various factors, such as waiting for approvals, dependencies, or external resources. Identifying and addressing these bottlenecks and delays can improve the efficiency of the development process.

  7. Defects: Defects or bugs in the software can be costly to fix, both in terms of time and resources. Focusing on preventing defects through practices like code reviews, automated testing, and continuous integration can help reduce this waste.

Students are asked to watch the lectures, download the resources and contribute in our discussions.

Upcoming course events you should be aware of include  bonus lectures, job aids, templates and guideline.

Who Should Attend!

  • SW Development Manager, SW Development Team Manager, SW Development Team Leader, Scrum Masters ... etc.

TAKE THIS COURSE

Tags

  • Software Development

Subscribers

2378

Lectures

8

TAKE THIS COURSE



Related Courses