The Benefits of Adopting an 'Agile-ish (Scrum)' Philosophy

Email     |     Share  
1 | 2 | 3 | 4 | 5 | 6 | 7
Previous The Benefits of Adopting an 'Agile-ish (Scrum)' Philosophy-1 Next

Click through for five benefits of adopting an agile-ish (scrum) development philosophy, as identified by Icreon.

“The goal is to give clients what they want, not just what they signed off on” says Sandeep Sawhney, CTO at Icreon.

What is Agile-ish (Scrum?)

The risks of waterfall development methodologies are widely discussed and documented: prolonged development schedules, team burn out, client communication lapses and compromised QA, amongst others. And agile has since become popular as the preferred alternative approach for software delivery across projects.

While, with some projects, agile is the only way to organize, there is no one-size-fits-all software development practice. As an increasing number of businesses request their projects be managed in an agile methodology, it is important that they realize the commitments involved and seriously consider “agile-ish” as an option.

Agile-ish = Agile with a Twist

So what is agile-ish? Agile-ish is a flavor of agile scrum development with a pre-development phase that involves an intensive specification process that outlines user stories and sets the backlog so the scope is defined and can be better priced out upfront. In agile-ish, the development phase itself is approached using the collaborative, iterative and evolving imperative of agile scrum processes.

This slideshow features five benefits organizations can achieve by adopting an agile-ish philosophy, as identified by Icreon.

Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.