How much project management is needed in an agile project using scrum? In terms of collaboration - what are the main differences in running one scrum team versus 11 scrum teams?

We have been part of a large Norwegian SCRUM project, SPK Perform, for almost two years. This has provided us with fruitful experience with project management in large scale system development projects using scrum.

Agile development originated in Smalltalk - this session will demonstrate why Smalltalk is still one of the best places to do fully interactive agile development. The presentation will be a short talk and demonstration melding test first with exploratory development.

Open Innovation is transforming how organizations manage their innovation processes. Open innovation fundamentally challenges how organizations innovate new product development ideas by extending the pool from which ideas are drawn. This model is concerned with combining internal and external ideas, as well as internal and external paths to market, to stimulate and advance the development of new products and technologies. Consequently Open Innovation has implications for how we view ‘the customer’ in agile projects.

The introduction of the agile practices is not so easy and immediate and each organization and it’s important to consider which impact agile may have keeping in mind the technology used by the organization that is usually the mirror of the background developers have.This session will drive you in the difficulties (and the solution put in place) experienced during the adoption of agile practices with Flash Platform developers, focusing on this points: -Tasks definition -Conversations’ output recording -Pair programming -Dependencies injection -CRC cards -Sustainable software

Here are some metaphors that I find useful when describing software product development. In particular, they are useful for describing the basic principles of agile development and the lifecycle of a typical agile project. Learn why software development is like releasing a music album, producing a magazine, staging a theatre production, or producing a film. I will present some justification for each metaphor, and describe how and why I find it useful. I will describe their usefulness as metaphors for software development in general, and for agile development in particular.

Adopting Agile as a set of “codified” practices mostly from the arena of Scrum an XP gets you so far, but what practices are for senior managers to do ?. What do they need to promote and how ? In this talk I will discuss some practices that we are using with senior managers to promote the agile culture including openness, learning , collaboration, reward systems, and technical excellence.

Agile processes focus on openness and transparency. Elitist developers embrace this, but many feel exposed and threatened by always having to answer for how every hour of the day is spent. Transparency in agile methodologies is a tool to promote cooperation. But often this transparency creates uncertainty and hostility. It can be used for playing the blame game between developers and it can also be used for micro management by managers. In order to turn the counterproductive blame game into cooperation, the team members need to be aware of this problem.

We, as Agile coaches, have faced our biggest challenge in May 2009. Energy sector waterfall project of 30 people in Norway, Sweden and Finland organized into regular 6 sub-applications wanted to achieve quite challenging targets. To grow to 70 people by setting up another teams in Czech Republic, to transfer 15 years legacy system knowledge and to be up and running with this all in 6 months.

Session’s topic is about how we fought and won over the challenges by implementing Agile to the project and how we have transferred the service to offshore location according to Agile principles.

So you deliver perfect code with no technical debt, on time and budget using Agile methods. Yet you remain unconvinced, and the resulting system is no success with users. But why? You even had an interaction designer onboard and “great UX” was part of the requirements list.

Our experienced facilitators will use examples of project failures to show how agile can mess up the best attempts at creating great experiences. Together we’ll discover why that keeps happening and what needs to be done to fix it so that your project can deliver a great experience and real business value that matters.

In the last few years the web has moved away from displaying static content towards being a platform for delivering rich client applications. Extensive DOM manipulation and AJAX callbacks are now fundamental to every Web 2.0 application.

Javascript is the language that has allowed this change to happen, yet it rarely receives the level of attention that it requires. This results in a risk which can jeopardise the delivery of projects.

We understand the value of good design and testing and we want to apply the same principles to our Javascript to ensure high code quality.