Ideas & Submissions

AgileVancouver is looking to our community to help drive the speakers for our fall AgileVancouver 2012 Conference, held in Vancouver from Monday October 1 to Wednesday October 3, 2012. If you have ever thought of speaking at our agile conference, submit your ideas and see what the community thinks. If you haven't, but are passionate about having a successful conference, give some feedback and help make the conference something special.

Ideas & Submissions

User Centered Design and Agile Development

Abstract: A friction often exists between User Centered Desgin (UCD) and Agile Software Development. On the one hand we all want to design a product that considers well the needs of the people who use it. On the other we want to deliver quickly through iteration and agile methodologies. It's not very obvious how these two ideas can be integrated... but they can. This session will cover how User Centered Design and Agile ...more »

Submitted by

Voting

15 votes

Ideas & Submissions

Eclipse Mylyn: Connecting Agile, ALM and the IDE

In under four years, Mylyn’s task-focused interface has gone from a university whiteboard to a tool with over a million monthly downloads. Not long ago, the notion of a tool that re-aligns the IDE around Agile collaboration and hides more of the program than it shows seemed radical. But as the task-focused interface continues its adoption, the next big step in the evolution of developer tools is becoming clear. In order ...more »

Submitted by

Voting

15 votes

Ideas & Submissions

Beyond Continuous Delivery

Continuous Delivery is the current pinnacle of agile development, but what lies ahead? Grounded in my own background and current work with continuous delivery, I will explore a number of ongoing and future concepts that could change how agile development and release works to achieve even higher levels of stability. Here are brief descriptions of some of the concepts I will be exploring: - Infrastructure as code- adding ...more »

Submitted by

Voting

12 votes

Ideas & Submissions

A hands-on Intro to Lean

Doing > Talking. This exercise will introduce concepts of Push vs. Pull, Kanban (bottlenecks, cycle time, work-in-process limits, idle/slack time, flow), Continuous Improvement (Kaizen), and Waste

Submitted by

Voting

10 votes

Ideas & Submissions

Branch-per-Feature in Agile

After wrestling with multiple approaches in work flow, branch per feature has emerged again in new light. Having the right tooling and skill set makes a difference to quality and the ability to deliver fast. Being able to deploy at any time is a business advantage. Rolling back only a single feature without resorting to toggles is a way to mitigate risk that superfluous code introduces. This talk will go into the how-to ...more »

Submitted by

Voting

10 votes

Ideas & Submissions

Technical debt: from metaphor to theory and practice

The notion of Technical Debt (TD) in software development was introduced in 1992 by W. Cunningham, and since then refined and expanded, notably by S. McConnell in his taxonomy, Martin Fowler with his 4 quadrants, J. Highsmith and I. Gat etc. As a convenient metaphor to expose many ills of software development, technical debt has received lately a lot of attention from the agile community. As a result of its success as ...more »

Submitted by

Voting

9 votes

Ideas & Submissions

I do not think that word means what you think it means.

"Agile" has become a word ascribed to just about every new process proposed to develop software over the last decade; so much so that it has become meaningless. I've encountered several companies using what they thought where "agile" processes when they were clearly not. The original Agile Manifesto, which defined what agile is supposed to be, has been co-oped by companies and consultants into a business of selling snake ...more »

Submitted by

Voting

9 votes

Ideas & Submissions

Temporal Agile

Agile is highly temporal. An "Agile team" today, will be completely different to the same "Agile team" a few moths later. This makes it extremely risky to claim: "we are Agile, and you are not." Or even worse: "in order to be Agile, you must ..." The secret is to understand why and how Agile changes for you, and how to compare the you of "Agile present" to the you of "Agile past," and the you of "Agile future." ...more »

Submitted by

Voting

8 votes

Ideas & Submissions

SAMPLE: Cynefin LEGO Game

ABSTRACT: The Cynefin LEGO game is aimed at those people who want a memorable introduction to the Cynefin model, a sense-making framework used to describe problems, situations and systems developed by David Snowden at the end of the '90s, that also turned out to be a pretty useful collection of tools for agile coaches. It can be used to understand which coaching technique to use in a specific situation, especially when ...more »

Submitted by

Voting

7 votes

Ideas & Submissions

Estimation is a four letter word.

Developers absolutely hate making estimates, and when you manage to finally get one out of them it's invariably incorrect. So stop asking. The definition of insanity is doing the same thing you did before and expecting a different result. If you expect tomorrows estimates to be better than yesterdays you need to change what you're doing. If you ask a company CEO where the stock value of his company will be next year ...more »

Submitted by

Voting

7 votes

Ideas & Submissions

Agile and the Iron Triangle Part II – A Retrospective

Presenter: Rob vanSpronssen Project Engineer at MacDonald Dettwiler for over 20 years This is a follow on from the presentation at the 2009 Agile Vancouver Conference titled Applying Agile Techniques within the Iron Triangle. In 2009 we had successfully executed a small project (9 months, 2,000 person days of development) using these techniques. Three years later we are at the end of a much bigger (2.5 year, 13,000 person ...more »

Submitted by

Voting

7 votes

Ideas & Submissions

Making Test Automation with Web Applications Work

In a perfect world we would have automated test coverage for every significant part of our web applications that consistently provides quick and useful regression feedback. In the real world automated testing efforts frequently fail because the tests are too time-consuming to author, too brittle when the underlying application changes, too flaky with asynchronous timing, or just flat out too slow. After way too much ...more »

Submitted by

Voting

7 votes