Posts

, ,

Our introduction to Agile course

 

Agile

We’re currently offering an industry leading Agile course…

  •   Don’t miss out on taking part in the UK’s most exciting and pertinent Agile IT course, provided by one of Europe’s leading Agile coaches.

Our next course is…

Introduction To Agile on 6th June’15

In this course, we focus on introducing you to the pragmatic world of Agile development, giving you the basic skills you need as a team member or even project manager of an Agile software development project. This course is suitable for individuals as well as small to large groups, and we can also offer private sessions at a time, date and location of your choosing.

More and more companies are adopting Agile methodology
Don’t get left behind!
Avail 15% early bird discount to all bookings before 16 May’15

Click here to book


AgileManc_FullLogo_Colour_RGB_2015

 

 

Capri Consulting are proud to announce their sponsorship of the Agile Manchester 2015 taking place in Manchester on 7 and 8 May 2015.  Whether you are new to Agile  or have more experience there is lots of interesting content for you with great speakers like Liz Keogh and Jurgen Appelo and 25 sessions, it’s going to be a productive 2 days!

We are very excited for the event to take place, as it is set to be a corner stone of the Agile industry for 2015. It is particularly exciting as Agile has been becoming more and more popular in recent years, with more and more companies adopting the Agile Methodology, of which we are advocates. Book your place now, as tickets are selling fast

http://agilemanchester.net/2015/tickets/

Make sure you come and check out the Capri Consulting stand and collect freebies! See you in Manchester!!

, , ,

Scrum team failing consistently?

We love firefighters! Don’t we? They are Heroes! But not in software development. In any Scrum software development, very few teams actually manage to find the time to refine and properly compose their stories (user requirements). Because of this, they’re constantly taking time to try and analyse the software requirements during the projects sprints.

This inevitably results in stories being rushed, ill defined, slapdash and careless. This delays the development of the software and  testing, which  should be a major activities, is compressed and squashed into just the last one or two days of the sprint.

And the result?scrum

Firfighting !!!!

The result, is of course, defect in the code. The team then starts firefighting, to try and fix the problems that were born of their ill planning. However, because they’re so caught up in their self-imposed firefighting, they don’t have time to analyse and create competent stories for the next sprint, so they dive right back into the vicious cycle of firefighting.