Let's say you're developing a Web Application that utilizes AI for livestock disease detection. Here's how you can apply Lean in your Agile process:
Identify Value: Prioritize features that enhance disease detection accuracy and provide timely alerts to farmers. For example, notification is primary feature that should be prioritize.
Eliminate Waste: Remove any unnecessary steps in the development process that don't directly contribute to these features. For example, since the process is quite straightforward, we don't need to create business process diagram
Create Flow: Streamline the integration of IoT devices and data analytics to ensure seamless operation. We use CI/CD to automate the build process and also use the flow.
Implement Pull Systems: Use Kanban boards to manage tasks related to device integration, data collection, and alert systems.
Empower Teams: Allow your team to make quick decisions regarding device configurations and data processing techniques. For example, technical teams invite vendor to discuss and to compare device configuration.
Build Quality In: Use automated tests to ensure the accuracy and reliability of disease detection algorithms. For example, we use NUnit to test the system.
Measure and Optimize: Track metrics like detection accuracy, response time, and farmer satisfaction to continuously improve the solution. we can use App Insight to measure the application perform and use Azure Open AI studio to validate it!
The Product Owner is not just a passive participant in the change process; they are active change leaders. They must embrace change, using it as an opportunity to innovate and improve the product. By fostering a culture of adaptability and continuous learning, the PO ensures that the team can navigate change successfully.
There are seven things that we need to execute:
Defining user value. On this step the PO should understand is the changes is major OR minor. A lot of minor changes can be majored
Managing backlog. PO should document meeting notes and versioning
Stakeholder negotiation. PO should arrange meeting with the customer to discuss the trade off and additional information
Prioritizing changes. PO should communicate with stakeholder to discuss the impact of the software development
Release planning. PO should understand the effect and technical review and adjustment
Risk management. PO should discuss the risk management because the changes
Acceptance criteria. PO should create structured to review the changes result
You can see the detail in this picture
On this article, we want to discuss about what artifacts that can be used for Lean Project management. There are several documents which are:
Commissioning list (features scopes). it discusses features and product backlog. it contains vision, scope. The scope contains features, user story, user, and estimation efforts
User story matrix. it contains matrix table for user story, users list, notification, and additional notes
Iteration plan. it contains iteration number, iteration date, and the user story
Regular report. it contains iteration number report, what already done, screenshot for each user stories that done, and additional question.
User manual. it contains features as heading 1, user stories as heading 2, and step by step usage scenario OR how to video as a normal content.