Application and Enterprise Architecture has been put through its paces in the agile world over the years: ideals (architectural work inside the development team, shortening the design-to-implementation loop as much as possible), misinterpretations ("We don't need no stinking Architects!" screamed the Keyboard Cowboys), and the inevitable backlash of misinterpretations, lack of craft, and the inertia of the status quo (Architectural Epics continuing to encourage a split between business and IT, command-and-control capital-"A" Architects).

Where are we now? What have we learned? More importantly, what have we forgotten?

Now more than ever, we need to go back to the core principles of agility and emergent architecture. Let's talk.

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • The Ideal: Emergent Architecture
  • The Misinterpretation: Cowboy Coding and The Mess
  • The Overreaction: Return of the Capital-"A" Architects
  • The Solution: Getting Back to Principles

Learning Outcome

Learning outcomes include:

  • Understanding the history of enterprise and application architecture in the agile development world
  • Common pitfalls, counter arguments, and misinterpreations of "Emergent Architecture"
  • Pros and cons of Emergent Architecture and its alternatives
  • Real-world Emergent Architecture techniques and practices, firmly rooted in first principles

Target Audience

Agile Architects, Coders, Craftspeople, and Process Gurus

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • 60 mins
    Workshop
    Intermediate

    Trying to figure out Agile Release Planning?  We've done it and we've done it well.  Twelve teams - done! Twenty teams - done! Forty teams - done!  If your organiztion needs to tackle the enterprise release planning beast, you should attend this session.  Whether you are struggling with planning a large agile release planning event or simply trying to figure out how to improve your current agile release planning events, this session will provide nuggets of learning from planning teams with hundreds of people spread around the globe.  Many organizations have tried to conduct enterprise agile release planning and gave up because they could not overcome some of the basic obstacles like who to invite, where to hold the event, and how to keep everyone engaged.  

    If you are trying to figure out how to coordinate two teams or dozens of teams, this session will provide insights into what works and what doesn't.  You will gain expereince by practicing actual agile release planning exercises to help you prepare for your orgainzations next agile RP event.  The learning expereince starts with a presentation on the key steps to consider as you launch a large agile program.

  • Andrea
    Andrea
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Project success =  f (listening, feedback, intentionality, practices) 

    To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

    Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

    This is a hands-on, try it out, concrete practice session.

  • Liked John Sextro
    keyboard_arrow_down

    John Sextro - Coaching Affinity Estimation

    John Sextro
    John Sextro
    Agile Coach
    9 Principles
    schedule 3 years ago
    Sold Out!
    60 mins
    Demonstration
    Intermediate

    Spend Less Time on Your Estimates

    Most teams would rather work to deliver value to customers than spend time estimating stories.  In order to spend less time estimating and more time delivering value to the customer, many teams have adopted “Affinity Estimation”.  Using “Affinity Estimation” many teams have significantly reduced the time required to estimate and I have personally been involved in sessions that used to take 60 minutes and are now taking 15 minutes.  By using “Affinity Estimation” to compare new stories to real stories that were recently completed, teams are able to quickly and confidently provide an estimate without lengthy discussions and worries of the unknown. 

    What to Expect

    The session will begin with a brief presentation highlighting everyday problems that coaches deal with when estimating stories.  Then, using volunteers from the audience, we will work through a series of exercises/games demonstrating the value of "Affinity Estimation" while teaching the audience and the volunteers how to coach these exercises for their own teams.

    All Teams are Not Created Equally

    This session will provide you with exercises that you can use for existing teams, as well as, new teams. 

  • Liked Philip Rogers
    keyboard_arrow_down

    Philip Rogers - Lean Coffee: Creative Uses of this Technique to Rapidly Surface Ideas and Encourage Team Collaboration

    Philip Rogers
    Philip Rogers
    Scrum Master
    NPR
    schedule 3 years ago
    Sold Out!
    30 mins
    Workshop
    Intermediate

    Lean Coffee is frequently used in meetup and conference settings. The beauty of Lean Coffee is its simplicity, and it is this very simplicity which makes it an appealing choice in various Agile team contexts. Specifically, Lean Coffee is particularly good for ad hoc training sessions and for retrospectives. The focus of this workshop will be on the use of Lean Coffee in these two types of settings, where we will split up into small groups and practice using Lean Coffee to cover ad hoc training topics and to do a mini-retrospective.

     

  • Liked Mark Hammer
    keyboard_arrow_down

    Mark Hammer - “Want to be Agile Across the Extended Development Team? Collaborate!”

    60 mins
    Talk
    Intermediate

    How can development organizations ensure building reliable systems, yet responsive to change? This is a fundamental question plaguing Agile organizations. The key is collaboration. Mark Hammer explores process changes and tools your organization can use to ensure high quality software, while maintaining the flexibility to respond to change. He highlights examples from large and small companies showing how simple changes can improve team performance, increase employee satisfaction and save the company money in expensive software fixes.

     The session highlights several key findings:

     1. PROCESS. Best practices for collaboration, focusing on what a collaborative culture looks like. How can managers foster collaboration? How can developers, testers and product managers work together to solve problems previously managed by just one of these groups?

    2. TOOLS. What tools can foster collaboration across these teams? And how can these tools be used to help teams adapt to new customer findings? I review several categories of collaboration tools, with special emphasis on tools that have impacted the ability of specific companies to collaborate and improve quality metrics and results.

    3. MEASUREMENT. Ways other companies have tried to measure collaboration and its impact on team performance, highlighting specific examples including companies that have put in place process and tools then measured their ROI against them.

     

  • Liked Howard Deiner
    keyboard_arrow_down

    Howard Deiner - Lean Thinking and What It Mean to the Agile Mindset

    60 mins
    Talk
    Intermediate

    Long before the Agile revolution for software development began, industry had learned that efficient production of goods required intense attention to quality, teamwork, and continuous improvement. These themes of Lean Manufacturing (which was further refined into the Toyota Production System) were never part of the original formulation of the Agile Manifesto, and are rarely mentioned as part of the traditional Agile/Scrum recipe for teams transforming to the new “Agile” mindset.

    The reality is that the traditional Agile/Scrum recipe is actually a “dumbed down” version of the Toyota Production System, and makes it easier for organisations to grasp and start from. However, if organizations really want to achieve the goal of producing the software they need in a fashion that leads to High Performance Teams and Sustainable Engineering, they will need to understand the principles of Lean so they can incorporate them into their unique process. This session teaches the basics of Lean, and demonstrates how they apply to Agile development.

  • 60 mins
    Workshop
    Beginner

    Many agile initiatives suffer from a feeble launch.  As Aristotle once stated “Well begun is half done”.  Performing the activities associated with developing a sound charter can help increase the likelihood of success for a team or organization .  

    Beginning with the end in mind, we use retrospective techniques to develop consensus around objectives, vision, and mission.  In this workshop we introduce the components of a good charter and how those components help focus the teammates toward a common goal.  In addition, the development of the recommended charter components ensures that key questions are succinctly answered during the kickoff of a team.

    Participants will learn the various types of charters and their recommended content.  During the workshop activity teams will develop a complete charter based  team of their choice or a provided case study.

  • Liked Gary Pedretti
    keyboard_arrow_down

    Gary Pedretti - Territories, Not Hierarchies - Using Pressfield's The War of Art to Enable Small Self-Organizing Teams, Intrinsic Motivation, and Organizational Change

    Gary Pedretti
    Gary Pedretti
    Owner
    Sodoto Solutions
    schedule 3 years ago
    Sold Out!
    3 mins
    Talk
    Intermediate
    Steven Pressfield's The War of Art: Winning the Inner Creative Battle is well-known to artists, especially with authors struggling with writer's block.  It's a bedrock inspirational tome, focused on the artist finding his or her true self, breaking through resistance, and contributing his or her unique gifts to the larger whole of society.
     
    If what we do when we create software isn't engineering, isn't factory work, and isn't science - aren't we saying it's creative work?  Art?  Craft?  We shouldn't be surprised that Pressfield's classic for artists chasing the muse has a lot to teach us in the technical realm.
     
    In this presentation, we'll focus on an important aspect of the book - the artist's orientation - of which Pressfield provides two possibilities, hierarchical or territorial.  We'll examine how this relates to "two pizza teams," product vision, software craftsmanship, intrinsic motivation, and effectively and appropriately breaking down organizational hierarchies.
     
    Be prepared for a unique, artistic view of our industry!
  • Liked George Paci
    keyboard_arrow_down

    George Paci - Running a Five Whys

    George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    30 mins
    Tutorial
    Beginner

    You're hit with a problem, possibly repeatedly, and it's not clear what to do about it.  You know that Root Cause Analysis can help, and you know a Five Whys exercise is a good way to do that.  But how do you run a Five Whys?  There's more to it than putting everyone in a room and saying "Why?" five times, isn't there?

    This session will prepare you to run your own Five Whys exercises, and to answer important questions like who to include, how to introduce the exercise, what to do when the group stumbles, how to deal with prematurely-offered solutions, and how to prepare for the exercise.