High-Tech Yuga

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 le...

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .

Challenge 1:   Team members are not adapted to Scrum to make estimate. At the grooming session involve with team and work along with them to convert epic in user story and break user story into task. Use Planning Poker or T-Shirt Size estimation technique to create estimate and involve them. So they see what the solution could be and how many effort it needs. Challenge 2:   The user stories are too big and not detailed enough. Release planning is the time entire scrum team work with product owner to discuss on the Epic to create user stories. Need to perform backlog grooming with Product Owner and Business Analyst during the sprint planning meeting to break user stories into small and doable. Challenge 3:   Almost all user stories are in progress till the last day of sprint. The first thump rule is the user stories with in the sprints should not depend on each other. Break user stories in to tasks which should be doable in a day. If you are using two week sprint foll...