article thumbnail

Kanban History: Origin & Expansion Across Industries

ProjectManager.com

Key Events and Books Agile Manifesto (2001): Defines the four key values and 12 principles of agile as defined by the software developers who created the document David Anderson successfully developed a kanban system for Microsoft XIT Sustaining Engineering Group (2004), which brought kanban from the factory floor to use in knowledge work globally (..)

article thumbnail

Agile Laws to Help with Transformation

Scrum.org

The idea has been around for several years: design the teams according to the product requirements and give them autonomy to create the best possible solution from both a value proposition and an organizational sustainability perspective. Waiting too long before shipping or pursuing perfection is not an option.

Agile 173
Insiders

Sign Up for our Newsletter

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

article thumbnail

Raising Climate Awareness in Scrum Teams - a Scrum Master’s Journey

Scrum.org

Then last year, as I was looking for ways to become more sustainable, the idea started to grow that at the bank I work for, in my own Scrum Teams, we could also take the sustainability perspective. Taking the sustainability perspective was a new approach for the team, but everyone agreed on its importance.

SCRUM 174
article thumbnail

Agile vs Waterfall: What’s the Difference?

ProjectManager.com

Commonly used in engineering and software development, it’s a more structured approach because progress falls in one direction, like a waterfall, from ideation to launch. Design : There are two parts to this phase, including logical design and physical design, all resulting in the software or product architecture. What is Agile?

Agile 397
article thumbnail

Quality Assurance and Testing: A Quick Guide

ProjectManager.com

Total Quality Management: Here the quality of the product is dependent on the participating constituents, some sustainable and controllable, others not. The Software Industry. In software development, quality assurance is a way to monitor the software engineering processes.

Aerospace 358
article thumbnail

Building blocks of the next generation of Organisations

Scrum.org

Having devoted communities aid in the organisation's ability to conduct its business, sustain itself, and produce excellent results. He has helped many organisations adopt agile software delivery practices, including large banking, payments, telecom, and product organisations. Co-workers ? Coworkers are no longer colleagues.

Telecoms 162
article thumbnail

How To Carry Out a Requirements Analysis

Wrike

Requirements analysis in software engineering . While requirements analysis is beneficial to any project, it is most common in software engineering. In software engineering, requirements analysis, known as requirement engineering, defines expectations for new software being built or modified. .