Emergent Design - Reality or Myth ?

The best architectures, requirements, and designs emerge from self-organizing teams. – Principle #11, Agile Manifesto.

Most teams transitioning to new ways of working struggle with the practice of emergent design in an Agile environment because they are so used to designing everything up-front. They have individuals in roles solely responsible for designing before teams implement that design.

Through this talk, I would like to share a real life case study , tools and tips on how teams can practice emergent design and its associated benefits.

 
 

Outline/Structure of the Talk

  • Brief Introduction to the topic and participant's awareness(5 mins)
  • Share real life experience of typical struggle faced with the practice of emergent design in a team ( 5 - 7 mins)
  • Share various options to overcome the challenges ( 7 mins)
  • Q& A ( 3 mins)

Learning Outcome

  • What & Why emergent design
  • Tools & tips to foster an environment of emergent design

Target Audience

Anyone part of Agile delivery teams

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Peter Stevens
    By Peter Stevens  ~  1 year ago
    reply Reply

    Dear Lopa,

    Thank you for your submission! 

    I like these aspects of the submission, and they should be retained:

    • Subject
    • Connection to real life
    • Short format

    I think the submission could be improved by:

    • Do you have slides or a video of this talk available?
    • I think your title needs a question mark
    • The target audience seems very broad. I would have expect very different focus depending on whether you are talking to stakeholders or engineers. It strikes me as irrelevant say for practitioners of Agile HR.
    •  a bit more substance about what you are going to say

    Could you kindly update your proposal 


    • Liked Jayaram Hegde
      keyboard_arrow_down

      Jayaram Hegde - System Thinking : A savior for Operation teams (Case Study)

      Jayaram Hegde
      Jayaram Hegde
      Agile Coach
      ANZ Bank
      schedule 1 year ago
      Sold Out!
      20 Mins
      Talk
      Intermediate

      Can we think of using System Thinking combined with Lean/Agile principles for Operation/Support Teams ?

      Agree, the most common thought is to use the Kanban approach. But will only Kanban approach can solve the problems for teams which are very much into executing ITIL practices for ages ?

      In organizations having significant operations in the area of Application Maintenance/BAU Agile implementation is not easy (forget about scaling in the first place).

      Considering the nature of work when compared to the product development space where the focus is on knowledge work significant changes required in cultivating Agile mindset (there is no text book/standard approach).

      Here in our organization we have tried and experimented on using Kanban (along with combination of Lean/System Thinking approaches) to create an agile organization that focus on automation, value driven delivery that efficiently support growth and enable to accelerate innovation.

      In this talk, you will understand how we have used System Thinking approach and lean thinking to achieve the above mentioned goals.

      Identification of bottlenecks through visualization and value stream mapping has helped in working towards waste elimination there by creating smoother flow in the system.

      Once the team is in a position to visualize the workflows they are enabled to focus on out-of-the-box thinking and work towards building innovative ideas to improve lead time of the end-to-end processes.

      Sufficient collaboration opportunities between business and teams would help to deliver the value there by establishing the agile mindset.