Remove 2011 Remove Definition Remove Lean Remove SCRUM
article thumbnail

Top 10 Lean/ Kanban Books for IT, Software and Knowledge Work!

Digite

Several good books have been written on Kanban and its application to various business processes, especially to Scrum, since David Anderson published his original Kanban “blue book”. This is the original book where David Anderson first laid down the definition of and guidance to the Kanban Method for software and knowledge work.

Lean 79
article thumbnail

Agile Transformation – Success Factors part 2

Scrum.org

Not only does the employees’ engagement matter regarding the topic of goals, but also the clear direction for the organization enables unexpected positive changes (for example, HR, Law, Finance - once they cooperate with Scrum Teams and Product Owners, frequently change their way of working and processes are simplified). 2] Ibidem. [3]

Agile 137
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Benefits of Scaled Agile Framework ( SAFe®) – Agilemania

Agilemania

The year was 2011 and there was a pressing need for a scaling framework that could help large organizations design efficient systems to build enterprise level products/solutions to cater to customer’s rapidly changing needs. SAFe is based on following 10 Lean-Agile principles-. We’ll be waiting for your comments. Author's Bio.

article thumbnail

The Kanban perspective on Teams

Scrum.org

The comparison between Kanban and Scrum obviously comes up often when we're talking to teams, especially in the context of Professional Scrum with Kanban. If you look at the definition of Kanban or Lean, you wouldn't find teams anywhere there. Scrum is quite clear about the topic (Quoting the Scrum Guide ).

article thumbnail

UX-Reifegrad-Modell: Eine Anleitung zur Entwicklung von UX-Fähigkeiten in Scrum Teams 

Scrum.org

State of Agile Report berichten nur 23 % der Befragten, dass sie Lean-UX-Praktiken in agilen Teams anwenden. . Die geringe Integration von UX-Praktiken in die Arbeitsweise von Scrum Teams ist für mich ein Anzeichen dafür, dass noch viele Scrum Teams einen niedrigen UX-Reifegrad besitzen. Level 0: Scrum ohne UX.

SCRUM 32
article thumbnail

Top Solutions to Project Failure – Epicflow Research Part 2

Epicflow Blog

Incorrect definition of project success. Varun Maheshwari , a Scrum Master at Telstra, says to “avoid project based thinking and start product thinking, have tight & fast feedback loops, make teams really autonomous, let team members talk to real customers so that they can understand domain & customer needs better, etc.

article thumbnail

Risk Management Resources

Herding Cats

5, September/October 2011. A Simulation-Based Risk Network Model for Decision Support in Project Risk Management,” Chao Fang and Franck Marle, in Decision Support Systems , Elsevier, 2011. Khadaka, and Dan Melamed, AACE International , National Capital Section, March 17, 2011. IEEE Transactions on Software Engineering , Vol.