Posts

The new courses…

FDP-ComputerTraining

 

Our next courses have just been announced, and are set to sell quickly:

23/05/2015 – Agile Master Class

30/05/2015 – User Story Writing 

Book either of these course now and receive a 10% discount using the code CAPTWT10. A further 10% of all booking fees will be donated to the Nepal Earthquake Appeal. Book here.

 

Capri’s Agile Masterclass is specifically designed to accelerate experienced Agile practitioners to a new level, led by Agile guru Krishna Thakur.
Using a mixture of discussion, instruction and exploration you will learn new techniques for development and testing, operations, automation and team dynamics, as well as working with legacy systems and integrating with third parties. Using these techniques you and your teams will deliver business solutions faster than they thought possible.

In a business, it is very important that the work being produced is well organised and priortised efficiently in order for it to be delivered at a high standard. Capri Consulting offers a specialist course in writing User Stories that can help you manage your work into smaller chunks to create tangible value.
User Stories helps us manage requirements. Their primary job is to define the value a user gains from the system. Since User Stories focus on the underlying Agile values of collaboration and Just-In-Time definition, it makes them a good Agile tool. User Stories are small narrative texts (2-3 sentences) in everyday/business language of the end user of a system. These capture what the user does, or needs to do as a part of his/her job function.

 

Follow us on twitter @CapriConsulting

, , ,

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.