A participatory workshop where coaches can share their experiences in coaching agile teams in hostile environments, what they did to avoid the pain, and how they turned toxic organizational inertia and attack against itself or circumvented the same to realize more agility. The session will be facilitated and will be oriented around capturing tricks, tips, and techniques, but will also allow for some sobbing and frustration and ranting. Epic fails are definitely welcome. The most sought after stories and ideas will be those which use the opposition’s own strength to advance the effort.
The method of Modeling in Color (MIC) has its foundation in object-oriented analysis and design; however, given today’s modern service oriented architectures (SOA), the approach is more relevant than ever. In any SOA, MIC can provide answers to difficult questions like: How are services properly designed? What’s the appropriate level of granularity for those services? Basic MIC techniques will be discussed and how to break a Color Model into discrete, loosely coupled components will be examined. How to convert the componentized model into XML schema and into XML web services will be explored.
Many Java teams want a more modern language that preserves their investment in Java technology. This talk looks at Scala, a new JVM language that fixes many of the limitations of Java. I’ll show why Scala is an ideal “upgrade” language for most Java teams.
Using examples, we’ll see that Scala is statically-typed, yet it has a succinct and flexible syntax. Scala traits add mixin composition to Java’s object model. Scala fully supports functional programming, which is the best approach for robust concurrent applications. All these qualities improve our agility.
This session will focus on the unique challenges companies face when using agile on projects that involve FDA governance: large company conservative culture, regulatory documentation, requirements tracing, and a bias towards waterfall development.
Skeptics argue that agile is best suited to small- and medium-sized companies and wrongly perceive agile as a limited, negating its use in the highly regulated corporate world.
In reality we will show you how we’ve successfully implemented agile in large sized companies operating in a highly regulated world.
Nonfunctional Testing has always been ignored and neglected because no one is sure what to do with it. Agile environments make Nonfunctional Testing more difficult as people try to invent ways to make it conform to whatever they are using. The goal of this workshop is to define methods to integrate and maneuver nonfunctional testing into agile environments. We will discuss the current concepts and determine the How, What and Why of Nonfunctional Testing.
Anyone who’s seen a user trying to get to grips with their application knows what a humbling experience it can be. No matter your design experience there’s no substitute for testing with actual users. But the whole user testing process can seem daunting & costly in terms of time, effort & materials. Seeing this Jakob Nielsen proposed a lightweight approach, ‘Guerilla User Testing’, in the mid-nineties. It emphasized what could be done on limited resources by a team committed to providing a decent user experience. Marc & Luke share over 20 years of experience applying this type of technique.
One of the core values expressed in the agile manifesto is “working software over comprehensive documentation” because working software is what delivers value to our customers. Agile development requires a sofware development team have working software ready to deploy at the end of each iteration; but accomplishing this can be harder than it seems, especially when first starting with agile. In this highly interactive session you will understand how a team definition of “Done” is necessary to making agile delivery possible, and what you can do to make it happen while avoiding the pitfalls.
In 2007, OpenView Venture Partners decided to adopt Scrum as best practice in software development in its portfolio companies and Scrum as the standard practice in all internal operations. The OpenView Scrum teams aggressively remove all impediments (take no prisoners). Attached is a reference model that supports best practices in management, sales, marketing, finance, development, and customer support in OpenView portfolio companies. After over 52 weekly Sprints, OpenView is the first non-software Scrum to provide a working manual on how to do Scrum outside of software development.
The biggest risk to most projects is building the wrong product. Regardless of how fast your agile team becomes, nothing matters if you’re building the wrong product.
In this tutorial we will look at both 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. You will leave with hands-on experience in very practical ways to prioritize a product backlog.
Traditional thinking holds that the more critical the application, the more tightly its development must be planned, staged, and controlled.