Skip to main content

Lean Thinking

Lean agile aims to eliminate wasteful resources and tasks for improved efficiency and reduced costs, while never sacrificing quality.

In fact, lean agile prioritizes bringing value to the customer with every decision that's made.

Lean agile is a development method that helps teams identify waste and refine processes.

The way of eliminating wastes are:

The figure of the Product Owner represents a clever way to speed up the flow of information between the customer and the developers. This reduces the risk of rework that so often appears in non-scrum development projects. 

Lean teaches us that each leader (Scrum Maser) must be in constant contact with his team and know each member well enough to understand the problems they encounter each day. This enables flow and therefore customer satisfaction.

Having cross-functional teams, lean tells us, allows for a quick flow of information, because waiting for the contribution of a team member from another function doesn’t happen.

In lean thinking, people must be empowered to solve problems and improve the work, because they are the ones who are closest to the process.

From a lean point of view, a checklist should be managed by the Product Owner in order to make sure everything is done according to client needs. In lean thinking we often talk about making sure that all information is “complete and correct” going forward.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more