article thumbnail

Five reasons why Scrum is not helping in getting twice the work done in half the time

Scrum.org

I worked as a product owner for my first product in 2007–08 to manage the insurance lifecycle for a major insurance company in America. They got the idea of increasing the complexity of dependency management and longer lead time due to the handoffs having individual accountability. Bad technical practices.

article thumbnail

Implications of Artificial Intelligence on Project Management

The IIL Blog

By Eugene Bounds and Steve Ackert Recently, the buzzword artificial intelligence (AI) has been on everyone’s minds, not just in the tech world but across many industries, including project management. AI technology will automate repetitive processes, generate insightful program reports, and highlight potential problems before they arise.

Insiders

Sign Up for our Newsletter

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

article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Transitioning from manufacturing to software engineering and development and various other industries, the Kanban Board has become a fundamental tool for visual management in project and workflow management, credited to the Agile movement. Columns might include "Ideation," "Design," "Approval," "Execution," and "Review."

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Developing a new product requires understanding of the users, of the technologies involved and what makes something valuable (or not). and Vidal, C.

2002 196
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. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. IEEE Transactions on Software Engineering , Vol. De Meyer, C.

article thumbnail

Estimating is a Learned Skill

Herding Cats

“Believing is Seeing: Confirmation Bias Studies in Software Engineering, “Magne Jørgensen and Efi Papatheocharous, 41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.