All posts by Herman Lintvelt

CT-SPIN #81: Simple Measuring

Event Sponsors

DVT Logo
Polymorph Systems web site

By using simple measurements it is possible to effectively quantify value and measure the workflow of various distributed agile teams, helping ensure that you are cutting fat and not meat when trying to be lean.

View Presentation Slides

Snacks and drinks kindly sponsored by Dynamic Visual Technologies

Wine kindly sponsored by Polymorph Systems.

Venue

Wednesday, 15 August 2012, 18h15
Bandwidth Barn’s NEW location,
3rd Floor, Block B
66 Albert Road,
Woodstock

Note: It is one of those old industrial buildings in Woodstock that is getting a revamp. If you enter through the entrance on Albert Road you have to walk all the way to the back (through a construction site). There is also an entrance on Williams St (around the back) which is closer to the lift/stairs. Their offices are in the corner of the building by Williams and Station St. There is parking on Albert Road, Station St and Williams St around the venue.

RSVP

Anyone is free to attend. Please RSVP at ctspin81.eventbrite.com. Alternatively, RSVP by sending YES or MAYBE via our contact form.

Continue reading CT-SPIN #81: Simple Measuring

CT-SPIN #75: Design in Agile Methods

DesignInAgileMethods-SPINCapeTown-20120215.pptx

Agile methods have some really good points: rapid feedback to customers who are considered part of the team, incremental building from a small, simple stable base, short time-boxed plan-do-show cycles, and continuous testing to prevent surprises. It is also interesting to talk about how agile methods approach designing systems. There seems to be a backlash against architecture, in the form of criticizing ‘BUFD’ – big up front design (thinking you can design for every eventuality before you really understand the requirements), and in the mantra ‘YAGNI’ – You aint gonna need it (never designing for the future, only putting the absolutely necessary things into your design as you need them). There has been quite some debate around these aspects, e.g. Are these valid criticisms of architecture? Do we need architecture in agile projects? Is there a way we can get the best of both worlds?

This talk is titled ‘Design in Agile Methods’, and looks at:
– design as art or science,
– engineering versus software design,
– the challenges of software design – urgency, complexity and uncertainty,
– two contrasting approaches to deal with these challenges (predict and control vs embrace change and learn),
– types of simplicity,
– cost of change, and
– how agile methods approach these issues in a specific way.

Event Sponsor:
Event Sponsor

Snacks kindly sponsored by Alacrity.
Wine kindly sponsored by Polymorph Systems.

Wednesday, 15 February 2012, 18h15
Events Room,
5th floor,
Bandwidth Barn,
125 Buitengracht Street,
Cape Town

Continue reading CT-SPIN #75: Design in Agile Methods

CT-SPIN #69: RESTful Web Services – A Journey

Today web services have become the standard way for inter-application communication and integration. While most enterprise web services are built based on SOAP, WSDL and the WS-* specification universe, a rapidly growing number claim they use a better way: REST, short for REpresentational State Transfer. In this talk, I will try to provide a pragmatic introduction to the fundamentals of REST and RESTful HTTP application integration, based on my personal journey from confused REST skeptic to fluent proponent.

Logo Open Box Software

Snacks kindly sponsored by Open Box Software.
Wine kindly sponsored by Yila Consulting.

Wednesday, 20th July 2011, 18h15
Events Room,
5th floor,
Bandwidth Barn,
125 Buitengracht Street,
Cape Town
Continue reading CT-SPIN #69: RESTful Web Services – A Journey

CT-SPIN #64: Taming the customer support queue: A Kanban Experience Report

Event Sponsor:
Event Sponsor

Update: This talk by Karen Greaves has been accepted for the Agile 2011 Conference, August in Utah. Be the first to hear it at CT-SPIN in February.

In Aug 2010 we reduced the size of our development team. We needed to handle customer support issues and new development with the 3 remaining teams. We had over 600 open defects and the list was growing daily. On top of that our first clients were going live. Clearly some radical change was needed. We implemented Kanban.

The result? In Dec 2010 we had no open severity 1 issues. Our queue was down to 54 issues. SLAs are met in most cases, and our resolution rate exceeds our incoming rate.

I’d like to share our story, and inspire you to tame your support queue too!

Snacks kindly sponsored by ScrumSense.

Slides: A Kanban Experience Report

Wednesday, 16th February 2011, 18h15
Bandwidth Barn
Cape Town

Continue reading CT-SPIN #64: Taming the customer support queue: A Kanban Experience Report