Remove 2006 Remove Influencer Remove Process Remove Software Development
article thumbnail

Practical Fibonacci: A Beginner's Guide to Relative Sizing

Scrum.org

A traditional or Waterfall software development lifecycle includes a long and detailed planning period to define requirements before beginning development. I have little experience or high time pressure; therefore, the estimate is influenced. 2006, Jørgensen and Grimstad). Trust the Team and the Process.

article thumbnail

The Ultimate Redmine Guide: How to set up and supercharge the best open source project management tool

Planio

There’s a reason startups are obsessed with “community” and influencers tell you to find your “tribe”. Even software. It was developed to help teams collaborate on the tasks, bugs, features, and steps needed to complete a project, visually track their progress, and plan their next steps using Gantt charts. What is Redmine?

2006 88
Insiders

Sign Up for our Newsletter

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

article thumbnail

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Managment Processes. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Making the Impossible Possible: Applying Heliotropic Abundance for creating Program and Project Management Processes. Event-Based Scheduling , 10 November 2006. Basis of Estimate Process.

2003 54
article thumbnail

Risk Management Resources

Herding Cats

México, 1 al 3 de Febrero de 2006. 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. Pich, Working Paper, 21/2006, Cambridge University, Judge Business School. “A De Meyer, C. Loch, and M.

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. México, 1 al 3 de Febrero de 2006. De Meyer, C.

article thumbnail

In-Depth: How Easily Biases Distort What We Believe (In The Workplace)

Scrum.org

Initially coined by cognitive psychologist Lee Ross (1977), it happens when people underestimate the influence of the situation on the behavior of others while overestimating the influence of their personal traits and beliefs (Berry, 2015). But the fact that some candidates “survived” the process isn’t enough to conclude that it works.

2015 219
article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

As we will see below, current scientific models for team formation underscore the need for time and frequent interaction to allow teams to develop the tissue that makes them high-performing. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner.