By Topic

Overcoming Traditional Project Release Reporting with an Agile Approach Focused on Change

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Samios, H.-P. ; Security, Gov. & Infrastruct, Intergraph Corp., Madison, AL, USA

If you are an Executive in a large organization Scrum / agile helps address a number of issues that you face in releasing products - improving quality, predictability, engagement of your people, and productivity. You've got help in the form of an Agile Coach and you understand that change is required to get these benefits, not only for the Scrum teams directly affected but also in the way you think about and approach development projects. The transition is making progress, and you are seeing improvements at all levels but you cannot help feeling that you've lost an understanding of the key decisions that the organization needs to make. You still have to run the business, to make commitments, and to release products. In the past you had information from the product teams that allowed you to understand where the issues were. That information seems to have disappeared. When you ask for it, you are given a “release burn-up chart” and are told that “Scrum means we respond to change” and “we don't do big upfront planning any more.” How can you get what you need and still be “Scrum”, still be “agile”?

Published in:

Agile Conference (AGILE), 2012

Date of Conference:

13-17 Aug. 2012