program selection system

Salesforce.com took a big bang approach to implement a SCRUM method, with huge success. This meant big changes to how Product Managers work, how we interact with the team, and manages dependencies between teams.

No more 200 page functional specs, no more waiting 12-18 months before features got into customers hands. No more changes to the release dates – how do we survive?

Is your agile project buried under a mountain of user stories? As you add stories, does your vision of the product you’re building grow hazier? As story count increases, do business stakeholders become more frustrated with prioritization? Do you find it difficult to communicate the big picture of what your system does?

Delivering value early and often is a well established agile practice. But rushing directly into Iteration 0 development can lead to tunnel vision (thereby building the wrong product) or unnecessary (thereby wasteful) refactoring. This tutorial describes what needs to happen between when a project is conceived by a customer and when software development can start in earnest. It identifies the artifacts (beyond story cards) that may need to be produced, whether and when they should be produced, which activities can be used to produce them and who should be involved.

Agile projects compel you to reconsider and redefine traditional requirements practices. There are agile benefits to leverage and pitfalls to avoid. In this talk, learn what to consider—including team and product factors—when you adapting your approach. You’ll discover agile requirements practices that promote and enhance of trust, what practices to calibrate, and the business analysis work needed by your project. Join us to explore ways to adapt and leverage your requirements practices to increase product quality and trust—while delivering business value on your agile project.

At the beginning of a project your stakeholders will invariably ask how much is it going to cost, what are you going to build, how long is it going to take, and how are you going to build it. To answer these questions you’re going to have to do some initial, high-level modeling of the requirements and of the architecture of the system during the initiation effort of your project. Agile Model Driven Development (AMDD) provides strategies to gain the benefits of modeling without the pain of needless documentation.

The biggest risk to most projects is building the wrong product. Regardless of how fast your agile team becomes, how brilliant your technical solutions are, or how many automated tests run continuously, nothing matters if you’re building the wrong product.

In this tutorial we’ll look at non-financial ways of both prioritizing product backlog items and choosing among competing project ideas. Included are relative weighting, theme screening, theme scoring, and Kano analysis.

—— begin 90 word abstract ——
How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The concept of “pull” from lean manufacturing challenges mainstream approaches to software development and reconsiders how value is delivered to the customer by inverting the thought process and focusing first on delivery. In this demonstration participants will experience how a real working system can be constructed from the ground up by employing popular industry “signals” to “pull” the creation of working software.
—— end 90 word abstract ——

Come and take it! Learn how to build the right system where each agent takes just what they need, just in time, to create value for the customer.

How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The kanban method and the concept of “pull” from lean manufacturing, in combination with agile values and practices, provide a powerful guide for how we can improve our profession by employing popular industry “signals” to “pull” the creation of working software.
By inverting the thought process and focusing first on delivery, “pull” challenges mainstream approaches to software development by reconsidering how value is delivered to the customer.

In this demonstration participants will experience how a real working system can be constructed from the ground up through the definition of executable specifications. See how through a series of micro-iterations, requirements can pull the creation of executable specifications, developer tests, production code, and refactorings.