Scrum.org

DECEMBER 8, 2023

So why is so much of software opaque to the business? I hear the phrase “but not all debt is bad” a lot, usually coupled with “some level of debt is manageable” and, as a software developer, it makes me cringe. From 2005 (first beta) until 2012 they worked, successfully delivering a new version every 2 years.

Underperforming Technical Team 173

Underperforming Technical Team Risk 2012 Cadence 173

The IIL Blog

FEBRUARY 14, 2024

The model uses the four aspects of innovation to make incremental changes to its existing capabilities, substantial or sustaining changes for more changes that require more than an incremental adjustment, adaptive changes to strategic policies, and disruptive changes to the overall organizational strategy.

2005 78

2005 2015 Innovation Certification 78

Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. The first Kanban system at Microsoft in 2005 produced productivity gains of 230%. The method wars. What have been your observations?

Agile 94

Agile Lean 2005 Risk Management 94

Project Pulse Journal

APRIL 3, 2024

As a result, project teams sustain meaningful and productive stakeholder relationships throughout the project lifecycle. An innovative approach involves using digital collaboration tools such as dedicated project management software, social media platforms, and interactive webinars. link] Verzuh, E. link] Xue, J., Shen, G.

Influencer 40

Influencer 2005 Innovation Technical Review 40

Herding Cats

MAY 10, 2019

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. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006. 3, March 2002.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

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. Dorofee, et.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 13, 2017

Have you made a cause and effect assessment of the problem to the solution, to the sustainment of that solution? ISO/IEC 17025:2005 (4.11.2) ‒ The procedure for corrective action shall start with an investigation to determine the root cause(s) of the problem. Will your solution actually prevent the problem from coming back?

Process 40

Process 2005 Manufacturing Engineering 40