Remove 2015 Remove Lean Remove Software Remove Technical Review
article thumbnail

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

Digite

Successful Evolutionary Change for Your Technology Business. 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. 123 pages, ET to Read: 2 hours, Published July 8th, 2015 by Pragmatic Bookshelf). By David J Anderson. By Mike Burrows.

Lean 79
article thumbnail

The Scrum Master Job (1): 4 Steps to Identify Suitable Employers or Clients

Scrum.org

The reasons for this are apparent, with software eating the world and the pace of innovation accelerating as the market-entry barriers of the technology sector are continuously lowered. Current tech trends — accelerated by the pandemic — threaten the very existence of many legacy organizations. Lean startup. Scrum Master.

SCRUM 191
Insiders

Sign Up for our Newsletter

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

article thumbnail

What Does SPCT Mean and How Do I Become An SPCT?

Agilemania

He encountered SAFe ® in mid-2015 when he was discussing generic topics during a discussion with a mentor about a generic topic that led to Agility at scale and his experiments with it. Once the person gets certified as SPCT, then he will become a change agent in the organization’s lean agile transformation and implementation.

article thumbnail

Risk Management Resources

Herding Cats

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol. Raz and E.

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The Development of Progress Plans Using a Performance–Based Expert Judgment Model to Assess Technical Performance and Risk,” Justin W. They cannot be suppressed or removed. 12, 2008.

2003 46
article thumbnail

Systems Thinking in Organizational Coaching

Scrum.org

Now we live in a world of digital technologies in a global post-industrial society. Systems thinking is a language and set of tools meant to illuminate our thinking about how the systems we are all part of actually operate (David Peter Stroh, Systems Thinking for Social Change, 2015). A software development effort is always a system!

2006 221