A series of cartoons depicts the terrible things that happen when agile practices aren’t followed. This session is valid for any persona, but especially for the product owner who will suffer when their product fails because they follow a process that isn’t helping their team deliver!
Deploying to servers has replaced shrinkwrapping CDs for delivering software. In the internet enabled era, the application is the infrastructure.
The basis of all Agile engineering practices is reproducibly building from source code. If software is delivered on servers, and those servers can’t be reproducibly deployed from bare metal to working services, how Agile can you be?
Continuous Integration is great, but what about Continuous Delivery! What are you waiting for?
This talk will outline innovations in tools, process, planning and culture emerging at the front lines.
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.
Most agile methodologies tend to assume that the team is co-located in a single team room. They give little guidance as to how to address team distribution although proven practices are starting to emerge within the community. The Microsoft patterns & practices team has been experimenting with distributed teams for several years, mining proven practices from the community and experimenting them out on numerous agile projects. This talk summarizes those learnings and proven practices and gives examples of their application - both good and bad - within our teams.