You have successfully coached a team or two, but seem to have lost momentum in spreading agile beyond your local division. The organization’s culture seems to be pitted against you. What efforts can you take to overcome this barrier? Do you know how to assess your current organizational culture? How about manage the changes to it? According to State of Agile Survey, for two years running, the ability to change organizational ...more »
Ideas & Submissions
Lessons learned from teaching and working with distributed agile teams.
Over the last three years I have worked with teams in 9 different countries, with every possible combination of distributed structure.
This talk examines what works and what doesn't work for distributed teams and presents some practical guidelines on ways to set distributed teams up for success.
In my work with teams and organisations around the world I have come across a number of anti-patterns in Agile implementations.
This talk will identify the common patterns, likely root causes and ways to prevent/overcome them.
The prioritized product backlog is core to being agile. A well prioritized backlog allows us to satisfy the customer through early and continuous delivery of valuable software. Lean and Kanban may call it something else, but there too, prioritized work is key. At the same time, prioritizing work is an extremely difficult activity. Internal customers, non-functional requirements, investigations, proof of concepts, and ...more »
The yelling is over, the features are prioritized, the experiments are designed. Now it's time to implement. How do you transition from idea to MVP (or beta) without (1) having to throw everything away when your user base explodes or (2) getting stuck in design and architecture hell? I'll take you through an experience-based, platform-agnostic approach to creating lightweight architecture and design that is equally useful ...more »
Who is responsible for QA on an Agile team? The answer is “Everybody”. And yet this is rarely the case. Often the Testers write their test cases and automation in isolation and execute them after development is finished. Developers write their code without talking to the testers except to understand how to reproduce the latest discovered defect. Product Owners elaborate requirements in isolation and then hand them off ...more »
Has your Software Development Department achieved the pinacles of Continuous Integration, but the rest of the organization is still wondering how they can benefit? Does it take you three minutes from a bug fix to integration tests results, but three months from an idea to a production code? In this case, you're ready for the next evolutionary step. Continuous Delivery is about enabling product innovation through frequent ...more »
From a purely technical perspective, you can almost say that Extreme Programming was a rebellion against the traditional concept of “Big Design Upfront.” We spent so much time explaining why BDUF was bad that we might have missed a better conversation on just how to responsibly and reliably design and architect applications and systems in an evolutionary way. I believe that the key to successful continuous or evolutionary ...more »
You've read about all the 'best practices', you've installed all the latest tools and frameworks, but somehow it doesn't quite feel like you're getting the benefits of agile development. Test-Driven Development is a simple concept that completely changes the way we design software. Instead of trying to remember and apply a long list of rules, we can use feedback from the TDD process to guide us in making our own informed ...more »
It can't be done! Android is a unique environment and there is no way to test drive it. This view is all too prevalent in the Android community. Join Cheezy and Levi as they dispel this myth. Watch this live coding presentation in which the dynamic duo test drive an Android application before you eyes. Watch as Cheezy keeps an outer loop of acceptance tests going to inform Levi to build the inner loop of unit tests ...more »
Building successful businesses is tough - especially for software startups. The principles and practices from lean startup and agile/lean development can certainly help. But what do you do if these approaches are new to the team? How do you strike the balance between learning, team improvements and delivering value? This is a challenge my recent startup, Printchomp, experienced and is still experiencing. In this session ...more »