program selection system

The evolution of purpose built Agile development environments is starting to have dramatic impacts on streamlining an organizations ability to adopt Agile processes and deliver new business applications. This session will provide insight into how OutSystems All-in-One Agile Platform and Methodology extend core Agile concepts with automation.

Danube CST Jim Schiel will discuss some of the best practices he learned from his own experiences with enterprise-level Scrum in a regulated environment, as well as those of other Danube CSTs. This will be an exciting opportunity to hear how large companies have conquered the challenges of scaling using the principles and practices of Scrum.

Code71, Inc. is a Web 2.0 solution and service company. Our target market is start-ups, small-businesses and non-profit organizations. We use on-shore + off-shore model using Scrum to deliver our projects. Our off-shore office is in Dhaka, Bangladesh.

Abstract

Over the last few years we have had the good fortune to aggressively apply the agile practices on a number of projects with great success. These successes, however, have not been achieved without challenges and lessons learnt along the way. This experience report specifically highlights examples from three different software development projects of varying sizes within this period and within the same organization. This is the story of three little pigs, where in all cases the pigs were well and truly committed.

The first principle of Agile is to deliver value to the customer. Understanding Business Value better can often do more than anything else to make your efforts better. We need to improve our Business Value Engineering.

In this Discovery Session, we intend to look at the principles and values that underlie Business Value and its uses. And we will look at how we practice Business Value Engineering throughout the life of the effort. Expect challenges, not pat answers. This discussion will enable you to improve your Business Value Engineering.

After three and a half years of using Scrum and still providing inconsistent quality and not getting better, we are embarking on an attempt to improve by using Lean ideas and modifying our Scrum implementation. For some time now, our attempts to make Scrum work for us have mostly failed. Scrum out of the box, in a company with over 100 developers and testers, was not working as expected. This presentation is a report of our efforts to improve our Agile approach by using Lean and other ideas.

Agile is now on most CV’s, so beyond the hype what is the future?

Many companies are now adopting Agile methods to hopefully fix problems with delivering software in a timely, sustainable manner. However, most people seem to think that the transformation will be quick, and that once implemented, people can proceed along, with little or no change throughout.

Scrum & XP may sound deceptively simple. But once you get down to the everyday practical stuff there are many subtle traps hiding about. Common mistakes that are easy to make and hard to detect, mistakes that cancel out many of the benefits that Agile methods were supposed to give. In this talk I’ll go through some of these traps, how to detect them, what the effect is, and what can be done about them.

A high-volume online poker system deployed prematurely and crashing every day. 50 (fifty!) consultants thrown in near the end to rush the release. The worst code anybody in the project had ever seen. Team members working 80 hour weeks.

This is what I saw when I started as CTO of a Swedish gaming company. 3 days into the job we crashed the national poker tournament and were thrashed in the tabloids. A few days later I was notified that half my team would have to go, just in time for christmas. Oh, and someone promised media that we would re-run the national poker tournament within 5 weeks.