In Agile you should start with the simplest thing that will give you value, and iteratively build on top of that. But how does that work with a Legacy Enterprise Application that everyone is terrified to touch? Or what if we need to build an application that handles millions of transactions a day? How can we make sure that our architecture will meet our needs two years from now, when we don’t know what the application will look like? And how does the process of architecture work in an Agile environment?

Join Chris and Shawn in this interactive session, as they explore these topics. Learn architectural patterns that allow you to evolve your architecture. Examine techniques to help you work with legacy apps and dependencies. Learn how good architecture allows us to manage technical risk. See how business and technical people can work together to build an incremental plan for your product.

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

Outline/structure of the Session

Start
Time
Length Topic
0:00 5 Introduction
0:05 15 Principles of good architecture - talk, group discussion, debrief
0:20 5 Evolutionary architecture - talk
0:25 10 Working with legacy systems - talk
0:35 15 Managing technical risks - talk, table exercise, debrief
0:50 5 Collaborative architectural and planning
0:55 5 Questions
1:00 Close

We could also do a 40 minute session by removing or simplifying exercises.

Learning Outcome

At the end of this session attendees will:

- understand the importance of evolutionary architecture

- be able to apply architectural patterns that support iterative development

- understand how good architecture allows testing and mitigation of risks

- be able to collaborate with their counterparts in product/tech in order to create an iterative plan

Target Audience

Architects, Technical Team Members, Product Owners, Managers

Prerequisite

This session will include discussions of technical patterns and practices, so some familiarity with architecture will be helpful. The session will also include discussions of the collaborative patterns necessary to ensure good architecture, which will not require technical knowledge.

schedule Submitted 4 months ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Declan Whelan
    keyboard_arrow_down

    Declan Whelan - Technical Debt is a Systemic Problem - Not a Personal Failing

    Declan Whelan
    Declan Whelan
    Agile Coach
    Leanintuit
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    You often hear technical debt described as a personal failing. Why didn't you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result of bigger, systemic problems.
    Chances are, you're not a bad person. You didn't want this to happen. It's the system, not you, that's chiefly responsible.
    In this talk, we will present some of the conclusions from the Agile Alliance's technical debt working group, which has looked into the systemic causes and consequences of technical debt. While marginal amounts of technical debt will always accrue, that does not explain why substantial technical debt is a widespread phenomenon. The organization in which software development teams work is the much bigger culprit. Many systemic causes, such as deadline pressures, under-investment in skills, and even the unwillingness to measure technical debt, conspire to create a growing burden on software professionals, who would otherwise choose not to create this problem if given the opportunity.
    Just as technical debt has systemic causes, the real cost of technical debt lies at the system level. The increasing drag on software innovation has effects not just on individual and team productivity, but on the software value stream, the portfolio, and the organization as a whole. Sometimes, the cost is obvious, such as the valuation of a start-up company's code; other times, the consequences are far more subtle and insidious.
    During this session, we will use the language and methods of systems theory to better come to grips with the causes and consequences of technical debt. Don't worry if systems thinking is unfamiliar — we will cover the basics during the talk. We will also do an exercise in which you will create a simple systems model of your own challenges with technical debt, and discuss how this model should help you shape a plan of action for dealing with technical debt.
    Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.

  • Liked Fawzy Manaa
    keyboard_arrow_down

    Fawzy Manaa - How to Lose Dev and Alienate Ops

    Fawzy Manaa
    Fawzy Manaa
    Senior Consultant
    Deloitte
    schedule 4 months ago
    Sold Out!
    40 Mins
    Talk
    Beginner

    As many organizations have adopted agile development and are starting to undertake a DevOps transformation to complete the lifecycle, it is not always easy to keep traditionally alienated back office practitioners engaged. In fact, many organizations go about engaging developers, testers, operators, ... in a way that does not align with the spirit of DevOps. Many enterprise DevOps transformations fail because of this very reason, this session will inform the audience of what it takes to create a strong and sustainable movement within an IT organization in today's world where people who perform different functions that are seemingly at odds can come together in the spirit of improving how work is done and delivered.

    The speaker will approach the topic from an anti-patterns perspective, highlighting the symptoms of transformation failure from structural, procedural, and strategic angles and discussing alternative approaches to enable DevOps transformation success.

  • Liked Steve Zhang
    keyboard_arrow_down

    Steve Zhang - The Joy Of Functional Programming

    Steve Zhang
    Steve Zhang
    Development Practice Coach
    Scotiabank
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    The popularity of Functional Programming is booming! Are you still wondering what all of the fuss is about? Come to this session and find out! This is an introduction to the power of functional programming. It covers functional programming's basic concepts, and shows you how functional programming will make software simple, elegant, easy to test, and lead to cleaner code. I will share my experiences learning, so you can avoid some of the pitfalls. So if you enjoy coding, love clean code, then you should start learning Functional Programming right now.

  • Liked Mishkin Berteig
    keyboard_arrow_down

    Mishkin Berteig / David Sabine - JIRA is the Worst Possible Choice

    90 Mins
    Workshop
    Intermediate

    A rant, with evidence, on why electronic tools in general, and JIRA in particular, are anti-Agile. Participants will use the Agile Manifesto to evaluate the electronic tools they are currently familiar with. JIRA is used as a case study.

    NOTE: Scrum asks us to have courage. The Agile Manifesto asks us to value individuals and interactions over processes and tools. I hope the organizing committee will consider this proposal despite the risk that it might offend some tool vendors. If we can't speak freely about our experiences with tools, we will fail as a community.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame / Aaron Sampson, PMI-ACP, ITILv3, SMC - Design Thinking for Organizational Change

    40 Mins
    Talk
    Beginner

    We all know how people use design thinking to create better products and deliver delightful experiences to our users. However, design thinking can be an excellent tool to use for organizational change. In the case of organizational change, our product is the change that we are trying to drive, and our customers are those people who are impacted (internally and externally) and have to live with that change. In the same way that design thinking puts the user front-and-centre for products, it can be used to put people in the organization front-and-centre. In this talk we will discuss how design thinking works and, as a case study, how we have applied it at Scotiabank to help drive adoption of the Bank’s NPS customer insights into building solutions that serve our customers. In that program, previous internal processes were ineffective in pushing relevant data to delivery teams at the right time. Using a Lean or Agile approach would have provided some benefit, but taking a design thinking approach uncovered an array of useful insights to make the whole process more purposeful. Learn from this example to explore how you might incorporate design thinking to drive greater effectiveness and relevance for your team’s body of work.

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey - Scaling Agile without the scaling framework

    thomasjeffrey
    thomasjeffrey
    President
    Agile By Design
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    Increasingly Agile adoption has focused on how to operate larger enterprises with agility, and run larger and larger initiatives, at scale.

    In many cases, organizations have turned to explicit agile scaling frameworks to address their needs to coordinate increasingly larger efforts to deliver value in a way of that does not sacrifice feedback and self organization . Often these frameworks attempt to address the complexity that comes with large scale by adding extra process and procedure. Prescriptive advice is prescribed in the form of additional roles, stages, gates, and methods. This approach to scaling bears more than a little similarity to the heavy weight methods of the past, but in this case merging agile terminology with much of the same framework bloat and bureaucracy we have seen in the past.

    As a a result adoptees struggle to understand how to fit these frameworks to their context, and seasoned coaches struggle to wrestle out the good bits.

    During this session I will discuss a different approach to scaling agile, one that places an emphasis on both mindset and practice. I'll pay particular attention to the topic of leadership, organizational design, and the role management has to play in designing a system of work that allows larger efforts to work with an agile mindset without being forced into a one size fits all process framework.

    A key part of the discussion will be to showcase how core agile methods and techniques can be extended and expanded to successfully manage coordinated agile deployments that range from hundreds to thousands of FTEs. I'll present these techniques by using real examples of agile deployments I have been a part of during my work with ScotiaBank's agile journey.

    Key Scaling Practices covered will include:
    - The design components required to structure your organization based on demand
    - How to continuously de-scale your organization
    - "Get Out Of the Boardroom" style governance and leadership
    - Operational cadences and Impediment Escalation Flow
    - Managing the flow of value at the Business Technology Asset level
    - Moving the conversation from stories to domains
    - Streamlining finance and budgeting to align to the agile mindset

    I hope to illustrate ways that both management and knowledge workers can select techniques that allow them to scale agile as needed to support ever larger initiatives without succumbing to a one size fits all framework that does not adapt constant change.

  • Shawn Button
    Shawn Button
    Agile Coach
    Leanintuit
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Beginner

    We are about launch our latest feature to the eager public, when suddenly we get the call all developers dread: The Site is down! Our business is pressuring us to quickly come back up, but we can’t even find the problem! We pick up the red phone and call Karen, "The Site Whisperer." She calmly spends five minutes typing, and announces that she found the problem, and everything is back to normal. Where would we be without Karen? How can we get these skills on the rest of the team, so anyone can work the magic she does?

    It turns out that troubleshooting is a learnable skill. Join Shawn as he explores the Science of Troubleshooting. This workshop will examine what is happening during effective problem solving. It will examine types of scientific reasoning, and explore how we are using them to solve problems, sometimes without even realizing what we are doing! Participants will see how, by using scientific reasoning and experiments to build and test hypotheses, they can greatly increase the effectiveness of their troubleshooting and debugging. By making the process explicit even consummate problem solvers can improve how they approach and solve problems. Using the awareness gained attendees can guide others to improve their problem-solving skills.

  • David Sabine
    David Sabine
    Scrum Trainer
    BERTEIG
    schedule 4 months ago
    Sold Out!
    60 Mins
    Experience Report
    Advanced

    Products are not Projects — simple.

    A project is:

    "a set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations."
    "What is a project? definition and meaning". BusinessDictionary.com. Retrieved 2016-04-19.

    Product development cannot be constrained to "certain cost" and products do not have a prescribed end date...so no "fixed period". So long as the organization finds innovative ways to meet market demands, the products they develop will evolve.

    So, why all the projects?

    I teach Scrum — it's a process framework that has been used to manage complex product development. Yet:

    • ~55% of the people in my classes are "Project Managers"
    • ~90% work daily in "project teams" (sic)
    • and ~0% are ready to let go of Project Charters!?

    Project charters in a complex problem domain create an illusion of safety, certainty, and confidence, but are wholly inappropriate in most organizations represented at this conference for one simple reason: the nature of our work is complex and therefore it is not possible to predict a "set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations".

  • Liked Alistair McKinnell
    keyboard_arrow_down

    Alistair McKinnell - Don't Settle for Poor Names

    Alistair McKinnell
    Alistair McKinnell
    Agile Coach / Developer
    Nulogy
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    I get frustrated with code that is sprinkled with poorly named classes, methods, and variables.

    Whenever I work on a team or coach a team, I put a lot of energy into choosing good names and sensitizing my teammates to the power of naming.

    I've noticed that developers spend most of their days reading code rather than writing code. I suspect you've noticed too. Creating understandable code is a high leverage activity for any team. And naming is where I start.

    The core of the session is an example that illustrates the process and power of choosing good names. The example comes from a recent project. There will be code.

    I will connect the example to specific techniques and patterns for choosing good names and share resources that you can use right away.

    My goal for this session is to sensitize you to the power of naming.

  • Liked Stuart Oakley
    keyboard_arrow_down

    Stuart Oakley - Multiple Intelligence Theory - An Agile View on How It’s Used

    Stuart Oakley
    Stuart Oakley
    Scrum Master
    Dealertrack
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    Agile teams are always working to discover how they can work best together. By exploring Dr. Howard Gardner's Theory of Multiple Intelligence, we can discover new ways of understanding our teams. With this understanding, we can better adjust how we work to improve teams.

  • Liked Shahin Sheidaei
    keyboard_arrow_down

    Shahin Sheidaei / Shawn Button - Community-Driven Change

    40 Mins
    Talk
    Beginner

    Many organizations flatten management structure when they transform to agile. It soon becomes obvious that important activities done by managers are still needed.  A community can fill these gaps. They can provide morale, governance, learning, and mentorship, recruiting and hiring, mutual support, coordination, sharing, innovation and more!

    Unfortunately few companies manage to create a strong community. Even fewer empower that community to fill these gaps. This means they are missing the ultimate benefit of community: a strong, empowered community can transform the organization itself!

    Join Shahin and Shawn in this interactive session to explore communities in organizations. Examine the benefits of building great communities. Learn how to spark the community, and how to support it as it evolves. Hear stories of communities empowered to improve the organization. Learn how to make a community into a driver of positive change.

  • Liked Ardita Karaj
    keyboard_arrow_down

    Ardita Karaj - Getting Freddie Mercury and Spice Girls together on stage

    Ardita Karaj
    Ardita Karaj
    Enterprise Agile Coach
    Tango
    schedule 5 months ago
    Sold Out!
    40 Mins
    Talk
    Intermediate

    Ever been in a situation when the Product Manager comes and asks for “a couple of small changes that are high priority” and the team says “They’re kind of big. Which one do you want first? Really, really!”.  “I want them all! As soon as possible.”.

    There are many directions one can go from here. One can work harder or work smarter. While you probably know ways to work harder, but let’s explore ways to work smarter.

    In this talk Ardita will share techniques that she has used which produce good results. She will talk about Product management, technical backbone, collaboration and how all to get Product managers and teams “singing” together in harmony and with focus.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Coaching Leadership in an Agile Transformation

    40 Mins
    Talk
    Intermediate

    How do you coach leaders in an agile transformation? How does coaching this group differ from coaching on an agile team? How do you coach Leadership as their peer? Agile is always thought of as being ‘down in the delivery layer’ of organizations. But, for us to be truly successful in embracing agility, we need to be more inclusive of all decision makers in the organization. That starts at the top. There are lot of cultural elements and tools that need to be changed across the organization. This requires dedicated change agents to be positioned within the environment of senior leaders to help them embrace agility in their everyday and strategic decision making. Most people want to do the right thing – it’s all about coaching so that, in the moments where our intentions and our decisions are tested by the status quo, we can help our leaders evaluate their choices. This means being a constant influencer, mirror and educator. And, it means sometimes you have to let things go. Successfully coaching leaders through agile transformation requires very purposeful influencing. In this session, we will discuss how to help bring senior leaders along an agile change journey as well as the primary challenges you are likely to encounter along the way and proven mechanisms to help you push through.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Design thinking and Agile: Infinitely more powerful together

    40 Mins
    Talk
    Beginner

    When Agile first came on the scene it was premised around putting the customer first. But, over the years its focus has evolved and the general perception of Agile today is that it’s mostly a tool for delivering software. Agile’s original focus was mainly on developers and testers, but it never really contemplated design thinking as a discipline. Design thinking, which has been around for decades but is only recently having its ‘moment in the sun’, compliments agile beautifully in that it focuses on trying to solve the right problems for the right people. Design thinking allows us to iterate and test assumptions before too much coding and production-readiness is done, which helps ensure the team is investing in the right things at every stage. It really provides a focus on innovating rather than simply burning down a backlog. In this talk we will discuss different ways to incorporate design thinking into the agile process. You will learn how to yield benefits from bringing these two practices together – most importantly how to best serve the users of the product or service you are delivering. At Scotiabank, we’ve been using these fantastic tools in combination for over a year. It is a journey, and although we haven’t completely solved everything yet, there are a lot of lessons we have learned that can be applied elsewhere.

  • Liked Sam Tabbara
    keyboard_arrow_down

    Sam Tabbara - How to truly transform large enterprises

    Sam Tabbara
    Sam Tabbara
    Agile Practitioner
    Bell
    schedule 5 months ago
    Sold Out!
    40 Mins
    Talk
    Intermediate

    Most important factors in any Agile transformation is the ability to react and change quickly, which are most often associated with startups than large enterprises. To really win and transform an organization there are core elements that need to be mastered and executed at the culture level. We will cover these elements and provide you real use cases where transformations both succeeded and failed to meet their potential to prove the relationship

  • Liked Gil Broza
    keyboard_arrow_down

    Gil Broza - Practice Does not Make Perfect: Why Agile Transformations Fail

    Gil Broza
    Gil Broza
    Principal Agile Mentor
    3P Vantage
    schedule 6 months ago
    Sold Out!
    40 Mins
    Talk
    Intermediate

    These days, almost every organization is showing interest in Agile. We seem to have all the ingredients for effective transformations: well-known practices, detailed processes, ever-improving tools, extensive literature, myriad certifications, and many consultants. How is it, then, that so few organizations are truly agile?

    Gil Broza, author of “The Agile Mindset” and “The Human Side of Agile”, thinks that one particular ingredient has been overlooked in the mad rush to adopt Agile. In this session, he leads us on an exploration of that ingredient and its place in an Agile transformation.

  • Liked Jason Little
    keyboard_arrow_down

    Jason Little - Deep Agile Transformation

    40 Mins
    Talk
    Advanced

    You may have seen that beautiful image of a caterpillar transforming into a butterfly on the cover of some consulting firm's 'Guide to Agile Transformation' whitepaper. Looks great, doesn't it? Unfortunately, that image doesn't show the ugly truth of transformation. A caterpillar stops eating, digests itself and dissolves all of its own tissue during the transformation process.

    Many organizations say they are transforming to Agile, but instead get stuck in a circle of either optimizing processes or buying an off-the-shelf method from a vendor. Then a bunch of people are forced into agile training bootcamps, a few agile projects are executed, and waves of consultants come and go, but over time, nothing is fundamentally different.

    If you're willing to be courageous enough to obliterate the status quo in your organization and put meaning back into your transformation, you'll love this session.

  • Liked Chris Gow
    keyboard_arrow_down

    Chris Gow / Shawn Button - This one tip can help clarify your requirements

    60 Mins
    Talk
    Beginner

    People are generally not great at understanding abstractions or novel ideas when we’re first exposed to them, but we’re pretty good at deriving abstractions or concepts given enough concrete examples. Including examples in requirements (whether that is by user stories, specifications or something else), will help teams understand the purpose of a requirement and lead to creative solutions.

    Join Chris and Shawn in this interactive session, as they demonstrate why including examples is useful and what makes an example effective. Learn how adding a few examples can help illuminate the purpose of a requirement and how it helps start conversations into unexplored areas. Learn about the various tools and frameworks that support automating examples. See how team members and stakeholders can work together to develop examples that can lead to unexpected solutions.

  • Liked Sriram Natesan
    keyboard_arrow_down

    Sriram Natesan / Nancy Wu - Adaptive Planning using Impact Mapping

    90 Mins
    Workshop
    Intermediate

    Have you ever felt you don't quite understand WHY you work on things that you do and HOW it actually supports your business' goals?

    Most (if not all) of us might agree that creating a shared understanding of the vision and goals is critical to the success of the organization. But how do we do it?

    From our experience coaching Product Owners and Product Managers over the years, many of them struggle with creating or articulating the business goals and how each of their product increments support them. It turned out that some of them were just taking marching orders from the powers that be, they didn't know (the goals) for themselves and their teams are left in the dark. This challenge is amplified by lack of definition and communication of measures of success to validate that the product increment is indeed contributing to the business objectives.

    These factors make it hard to answer questions like "Should we start working on this?" or "Should we continue working on that?".

    Fortunately, a technique like Impact Mapping helps overcome this challenge. Impact Mapping is a simple but powerful way of visualizing the mapping of the business goals or objectives down to the product increments that teams work on. It is a great tool that lends well to having meaningful dialogues between business, technology and other stakeholders, and most importantly useful for adaptive planning of what gets worked on or what should be stopped.

    In this session, we will share what Impact Mapping is and how to create one. By the end of the session, you will pick up enough knowledge through the process of creating an impact map to try it at work.

    This session is suitable for anyone that is interested in learning a technique to create connections between business goals and deliverables.

  • Liked Mike Kaufman
    keyboard_arrow_down

    Mike Kaufman / Joanne Stone - Improving Your Skills with Open Space Concepts

    60 Mins
    Talk
    Beginner

    Have you been to an open space? Did you remember how the facilitator’s held that space? Truth is, open space facilitators are very similar to servant leaders. Each create a space that promotes safety, collaboration, empowerment with little direction and very simple laws. We invite you to explore how to apply the open space concepts to Servant Leadership and our Agile Teams.