Agile Delivery Model

Now let’s take a look at the Scrum framework. Scrum is the best known and most widely adopted agile framework in the world today.[1]  With its emphasis on delivery high quality solutions faster and continuous improvement, Scrum teams value commitment, openness, and respect.

Agile teams respond to change by focusing on the customer’s immediate needs and by not doing anything that is not required immediately.  The Product Owner, the person that best represents the customer, selects the stories (or feature) that provides most valuable to the customer, and the whole team works on that feature.

  RTC ALM for Scrum


Agile is about delivering software as soon as possible, and then regularly and frequently. Scrum teams focus on working on valuable tasks each day until the PO is satisfied.

Rapidly responding to change and delivering in short intervals is often the most challenging part of adopting agile for those people who have spent most of their careers working with a traditional or waterfall method.

In addition, agile is about enjoying your work. Agile team are self-organizing, meaning the team, and everyone on it, is empowerment to make decisions that would otherwise be made by the project manager.  For example agile teams estimate their own work, work with the PO to decide which stories are prioritized for delivery.

Finally, Agile is about using the knowledge, ideas, and inspiration of everyone in the company.  Agile teams take time out to reflect on the recent past and to identify ways removing blocks or impediments to producing high quality code.

[1] Core Scrum — Values and roles,


About the Author Reedy Feggins, Jr, is a Solution Architect and Agile Coach at IBM Software, a global software development company. Reedy is a certified ScrumMaster and PMP certified Project Manger. In this role, he trains, mentors and coaches teams in implementing practices such as Scrum, XP and Disciplined Agile Delivery (DAD). Reedy is also a IBM subject matter expert (SME) supporting the adoption of several IBM software development tools: Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Requirement Composer (RRC), RequisitePro, ClearQuest and ClearCase. He has extensive experience mentoring teams over the past four years has given him the ability to assess business needs, craft an adoption strategy and provide organizations with practical experience implementing the appropriate Agile adoption strategies. My Linkedin Profille

Posted in Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 88 other followers

Blogs I Follow
Agile and ALM

Swimming against the waterfall...


Web Management. Simplified.

BJ Dooley's IT Toons

Cartoons by BJ Dooley for the IT industry.

Disciplined Agile Delivery

An agile process decision framework for the enterprise

Dan Toczala's Blog

THINK - About what's possible....

Best Practices for Building Software Platforms

Best practices, methodologies, technical observations, and other stuff for building better software. Authored by Jim Ruehlin.


Technology and Project Management: through the eyes of a hired gun

The Blog

The latest news on and the WordPress community.

%d bloggers like this: