New shared Agile resources

Why did we develop these resources?

We saw the advantages of using Agile techniques, but the established frameworks didn’t sit well with our existing project processes. We cherry-picked the elements of Agile that we felt would work for us and pulled them together into our own take on Agile.  We’ve learned from our experiences over the last  years and we are now keen to share our experiences with others.

These resources were developed by Dawn Holmes from Project Services and Bill Lee from Software Development.

“This framework is a valuable resource for anyone starting out with Agile. Based on Scrum and developed by IS Apps over many years to fit into University practices” – Bill Lee

What is Agile?

Agile is a framework based on iterative and incremental software development where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change

Why use it?

There are times when a more traditional approach to developing services isn’t efficient. Perhaps it’s a new service where detailed requirements aren’t yet clear, or there’s a need to get a simple service up & working quickly whilst the more advanced features can be delivered over time.  Under these circumstances a more iterative & incremental approach to developing the software would be more appropriate. This helps to deliver a quicker return on investment.

Agile ROI

Framework for Agile

In IS Applications, we have developed our own Agile framework, taking elements of best practise from several recognised frameworks such as Scrum, XP and DSDM (Atern).  it is a collection of Agile techniques and practices which abide by the Agile Manifesto and the 12 principles of Agile.

principlescropped

Which projects work best with Agile?

It works best on software development projects where there is a discreet new solution required. Agile techniques can be used on other types of projects but it lends itself more readily where you’re developing something from scratch.

A second key condition for success relates to the iterative nature of Agile. This approach allows the business partners to see the solution evolve and mould the outcome through close collaboration with the project team. A close working relationship is particularly important on an Agile project where the software is developed incrementally and needs frequent decisions and input from the business..

Agile decision tree

How do I find out more?

By accessing our free Agile resources page here

 

Leave a Reply