• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!


Agile Adoption in non-Agile Organizations

Page history last edited by margaret motamed 15 years, 1 month ago

This page is a collections of links to files and pages that describe how Agile practices may be adopted in organizations and environments where Agile is not the primary practice and may not have support at all levels of the management hierarchy.


Bridging the gap, Agile Projects in the Waterfall Enterprise, an article by Michele Sliger http://sligerconsulting.com/Bridging%20the%20Gap.pdf  Describes many tips and practicals for the “murky transition period when agile and waterfall are forced to coexist” during initial agile adoption.  posted 4/28/09 MMotamed

Selling Agile: How to Get Buy-in from Your Team, Your Customers and Your Managers, a webinar  by Michele Sliger  (free registration) http://www.versionone.com/agile_webinars_101.asp#sellingAgile  “…focus first on the general idea of a sales pitch, including what to do and what not to do. Then we’ll look at selling agile to the team, to management, to the customer, and to others in your organization. We’ll wrap up with a pointed look at not selling, and instead focus on finding other ways to promote and share agile.”  posted 4/28/09 MMotamed

APLN06 - David Hussman and Tor Stenstad - GMAC/RFC Agile Transition , a podcast of a presentation by David Hussman and Tor Stenstad http://agiletoolkit.libsyn.com/index.php?post_id=118607 An experience report about Customizing Agile for a large implementation. Discusses; inclusive chartering  for the transition, mapping the project community of builders (venn diagram of everyone who works on the project), stop before you start – make a backlog, personas, engage the real product owners, smagile, converted some engineering managers into coaches, start with a consultant and gradually fade their involvement5/04/09 MMotamed


Comments (2)

Wayne Mack said

at 8:42 am on Apr 25, 2009

In my situation, contracting work for the US Federal Government, it is rare that we have top-to-bottom commitment to agile. I suspect this applies to others as well. The questions I am interested in are:

1) What are the levels of agile that I can apply and what is the value proposition arising from each of these levels?
2) What are techniques for growing the agile adoption level, especially when going across contractual boundaries?

Venu Tadepalli said

at 12:18 pm on Apr 25, 2009

I have used agile on FP state contracts with milestone based payments.
Bottom-line is we have to start quickly and within the available wriggle room.

In the first contract, for each milestone we attached deliverable and defined done criteria. Apart from adding two additional documentation artifacts, it did not add much complexity to the project. By the time the contract was done every one was used to agile terminology (prioritization, product backlog, time box, velocity, done criteria, sprint demo, retrospective etc.) and it was easier for the future business.

You don't have permission to comment on this page.