Leveraging the “B-side” of the Agile Manifesto
Outline/structure of the Session
Below is an outline plan for the walkthrough. There will be a few excerpts from videos shared to provide complementary insight and humor in the presentation, but I’ll have a local copy to prevent any risk of Wifi streaming issues.
• Process & Tools in our new Agile era of Individuals & Interactions
Try to run your agile organization without any process or tools and you get chaotic agile. While development is never all about the process or tools, we must avoid clinging to process & tools as an excuse to avoid the real thinking and engagement required through individuals and interactions. You can’t cookie cutter the model for your organization, but we’ll discuss the more popular options out there and discuss the proper considerations for the B-side role to be played.
• Comprehensive Documentation in our new Agile era of Working Software
Technical Writers as Dinosaurs? Not so fast. Like a railroad engineer who sees that the mechanism of transporting people is evolving, there is still a need for this role in many emerging agile organizations. The advent of distributed, collaborative, and social documentation mechanisms actually can suffice for documentation.
• Contract Negotiation in our new Agile era of Customer Collaboration
Until customers know what they want before seeing the final product, some level of contract negotiation must always apply in software development. A country’s legal system may drive the current world of contracts, but there are new lightweight agile contract templates that have proven highly effective for agile engagements which enable real business partnerships rather than classic customer/vendor dysfunctional dynamics. Some walkthrough examples will be shared for the audience to understand the ideal context for contract negotiation. Tips provided for setting up the customer collaboration model will be essential for agile contracts.
• Following a Plan in our new Agile era of Responding to Change
Responding to change doesn’t excuse us from planning. But planning has changed significantly in the agile world. Roadmaps and Release Plans still have a place, but what about folks in the organization still trying to see the detailed Gantt charts? We’ll discuss how to best incorporate the value of a plan, while still ensure that your organization is optimally established for responding to change. Those approaches for doing so will leave the audience with a thoughtful set of concepts to bring back to their organization. The line on plan following against needs for change is delicate, but manageable with the outline strategies that will be discussed.
PLEASE NOTE: The link to the slides below are the only public presentation slides that I have been able to post with Equifax legal and marketing approval. I also had to "gut" several sections and images from the posted slides, although typically receive approval to show much more content - it just can't be posted or distributed.
Individuals who finding real-world pressures toward the “B-side” items of the Agile Manifesto & want to learn/discuss some balancing approaches.