article thumbnail

Basis of Estimating Software Development

Herding Cats

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Estimation: Demystifying the Black Art , Steve McConnell, Microsoft Press, 2015.

article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002).

2010 229
Insiders

Sign Up for our Newsletter

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

article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

Some find the process of creating them “childish” or “a waste of time”. Note that we’re using functional job titles here for clarity; not all companies use them, and the Scrum Guide only talks about “developers”. You can fast-track this process with good work agreements. In Achieving Quality in Software (pp. Kearney, E.,

2004 228
article thumbnail

The Project Manager’s Agile Transformation Journey

The IIL Blog

My Keynote Presentation is about the development of project management and project managers in the Bosch Group. I will focus on two selectively chosen business units that have already gone through the agile transformation: ETAS (Bosch’s Software Development Subsidiary) and Bosch Power Tools. Johannes is an B.Sc.

Agile 88
article thumbnail

Process Reduces Agility? Only on De Minimis Projects

Herding Cats

A popular toss off aphrase in some agile circles is process reduces agility. I've been in the software development business for 30 years, mostly in the Software Intensive System of Systems world, where embedded systems are 100 times more prevalent than business, web and desktop systems. VanderLeest GLSEC 2008. "A

Process 39
article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141
article thumbnail

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 200