There is nothing ‘Agile’ in the current distributed Agile project management systems, which is focused towards passively capturing and providing information to teams, they are traditionally designed for people who have no choice but to use, which are ‘transaction oriented than ‘relationship oriented’ this is really ‘anti Agile’.

This discussion / talk is inspired by Geoffrey Moore concept of systems of engagement . This discussion / talk is intended to

a)      Provoke thought on how to bring ‘Agile’ values and principle in transitioning from current Agile project management system designed around discrete pieces of information ("records") to systems which are more decentralized, & relationship oriented which embraces social behavior of a team.

b)    Talk also brings out following uniqueness of Systems of engagement and how can we achieve it in distributed Agile context

Systems of Engagement – Distributed Agile 2.0

Systems of Records ( current Agile project management)

High complexity

High volume

Relationship oriented

Transaction oriented

Outgrowth of project teams

Outgrowth of value

Organize around orchestrator

Organize around concentrator

Focus : Expertise, innovation and market development

Focus : efficiency, speed, and adaptability

 

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

Outline/structure of the Session

Current Distributed Agile project management - focus & weakness - 5 minutes

What is ‘systems of engagement’ and how can we map it to Agile values and principles – 10 minutes

Adopting ‘Systems of engagement’ ideologies to distributed Agile project management – 15 minutes

How does a Distributed Agile 2.0 will look like - 5 minutes

Q&A and discussions – 10 minutes

Learning Outcome

Overview of Practices that makes your distributed Agile project management really ‘Agile’

Steps involved in creating a ‘Systems of engagement’ based distributed Agile 2.0

Possible tools and engineering eco system to facilitate this.

Target Audience

Agile program managers and project managers of medium to large enterprises

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  4 years ago
    reply Reply

    Hi Prasad,

    Thanks for the submission. Please find my thoughts below.

    Topic Synopsis: There is a lot being talked about and some of them are in itself main topics which I believe will be quite difficult for the participant to go through and understand. It will be good if you have crisp and concise problem on what the talk is about which attracts the participant come to your session.

    Process: Suggest choosing 3-4 areas that you want to discuss. Given that the session will be for 45 min it might be difficult to cover all that is outlined.

    Learning Outcome: Add 4-5 crisp bullets that the participant can take away and start implementing when they get back to work post attending the conference.

    You can help us in our decision making if you can share links to blogs/presentations on this topic or other presentations.

    Looking forward to see your revised submission.

    • Prasad
      By Prasad  ~  4 years ago
      reply Reply

      Ravi,

      I have updated the submission. I have shared the inspirational links for this talk. I am in prepration of a deck in line with what I have proposed, will take few weeks to complete a first cut of it.

      Let me know if  any more inputs are required at this point in time

      Regards

      Prasad

  • Sudipta Lahiri
    By Sudipta Lahiri  ~  4 years ago
    reply Reply

    Hi Prasad,

    Can you pls give the next level of detail to help understand what will you be covering... I do find this at the very high level to get a sense of what you will be trying to cover.

    Hope to hear from you...

    Best wishes
    Sudipta.

    • Prasad
      By Prasad  ~  4 years ago
      reply Reply

      I will be updating the submission with more details

  • Naresh Jain
    By Naresh Jain  ~  4 years ago
    reply Reply

    Prasad, request you to please respond to the comments below.

  • Sudipta Lahiri
    By Sudipta Lahiri  ~  4 years ago
    reply Reply

    Just another thought... a little bit of background on the experience that has helped you to build this content will also be helpful.


  • Liked Nikhil Joshi
    keyboard_arrow_down

    Nikhil Joshi - Build - Measure - Learn : Without spending a fortune

    20 Mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Tathagat Varma - Agility @ The Scale of Busine$$

    Tathagat Varma
    Tathagat Varma
    Founder
    Thought Leadership
    schedule 4 years ago
    Sold Out!
    45 Mins
    Case Study
    Advanced

    [24]7 Customer, Inc started out in customer service space from Bangalore in 2000. Today, it is a sucessful mid-size company in voice-based customer support that also creates IP and products in big data and predictive analytics for some of the biggest names in business, and is a a high-growth company headquartered out of US. The growth in product R&D happened both organically as well as from acquisitions across multiple geos. While the initial / startup stage processes had been extremely successful in building the company's strong foundation, it was felt that the next stage of growth might not be a linear extrapolation of the past successes. Recognizing this futuristic need, it initially embraced agile software development methods in Q1 of 2013 to improve responsiveness, predictability and time to market in the product development organization. In Q2 of 2013, it embarked upon an ambitious company-wide program. The charter was to establish an end-to-end execution framework to make the entire operations efficient and effective - right from marketing and pre-sales to delivery, deployment, operations and ongoing optimization. 

    In this session,

    • We will analyze challanges involved in scaling-up agile adoption outside the software team across the entire organization.
    • Specifically, we will also discuss how we addressed some of those unique challanges that are associated with growth and scale, and
    • What does it take to achieve true end-to-end agility. 
  • Liked Ashish Mahajan
    keyboard_arrow_down

    Ashish Mahajan - Water the root , Enjoy the fruit

    Ashish Mahajan
    Ashish Mahajan
    Agile Coach
    Shell
    schedule 4 years ago
    Sold Out!
    20 Mins
    Talk
    Intermediate

    Yellow or dry leaves of a tree have more to do with its root, rather than its color, which is just an indication of need to water the roots. For a tree to flourish, to bear green leaves, with fruits, it’s the root that needs to be watered

    This is to say, put focus and care into your core every day and then the rest of the things will simply flourish and express itself.

    At times, we are too busy in discussing and analyzing things at a very high level, trying to improve the color of the yellow leaves of the trees, by applying patches, thereby ignoring watering its root.

    We are so obsessed with achieving better results every time, that ,metrics, processes and numbers become the focus of discussion in the organization. We keep on doing the same thing again and again, and expect different results, every time.

    Measure more, measure accurately, implement jazzy-flashy processes with new fashioned terminologies of promises of skyrocketing results, make everyone occupied, and reduce cost at any cost!

    And most of the times, you get the same results, or even worse.

     

    Here are some of the things,I believe, are watering the tree of Product Development that bear the fruits of success.

    • Focus on automated unit tests and refactoring the code every time you see an improvement opportunity, quality will take care of itself.
    • Focus on having open, honest and professional discussions with customers; trusted partnership will take care of itself.
    • Promote culture of failing fast and encourage making mistakes, time to market and innovation will take care of itself.
    • Implement the DNA of Value Flow into the organization, and cost will take care of itself.
    • Focus on respecting and improving skills of the people in your organization, the results will take care of itself
    • Destroy the cubicles , both physically and mentally,  and the waste will have a tough time to find a place.
    • Focus on building great teams; and great products will take care of itself.
  • Liked Ted Tencza
    keyboard_arrow_down

    Ted Tencza - Creating a Great Engineering Culture in an Agile workplace.

    Ted Tencza
    Ted Tencza
    Director of Engineering
    Bigcommerce
    schedule 4 years ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Company culture, or its DNA, is one of the most important factors to determing if a company succeeds.  Many companies claim to have great company culture.  But what does this mean, how can you know if your company has a great culture, and how can you go about improving the culture?  This talk will explore what great companies have in common, and share experiences I have had in helping to develop engineering culture during my career.    

    Will also explore how Agile principles help to foster creating the best possible culture for your organization.

  • Liked Dinesh Sharma
    keyboard_arrow_down

    Dinesh Sharma - Thinking Environment - Do you have one?

    90 Mins
    Talk
    Advanced

    Everything we do depends for its quality on thinking we do first. Our thinking depends on the quality of our attention for each other.

    A Thinking environment is the set of ten conditions under which human being can 'think' for themselves - with rigour, imaginaton, courage and grace. A Thinking Environment is natural, but rare. It has been squeezed out of our lives and organisations by inferior ways of treating each other.

    Thinking environment is based on ten behaviours that generate the finest thinking, and have become known as The Ten Components of a Thinking Environment. These components are

    • Attention,
    • Equality,
    • Ease,
    • Appreciation,
    • Encouragement,
    • Feelings,
    • Information,
    • Diversity,
    • Incisive Questions and
    • Place.

    Each Component is powerful individually, but the presence of all ten working together gives this process its transformative impact.

     

  • Liked Prasad
    keyboard_arrow_down

    Prasad - Agile in Marketing, sales and pre-sales of Service Company

    Prasad
    Prasad
    Prasad
    HolleyHolland
    schedule 4 years ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Owing to internal and external demands and market place pressure, Services Companies have learned the hard way of executing the projects in agile like way. Irony is that, most of the contracts / Master Service agreements / Statements of work remained traditional ‘legal’ intensified subject matter. This is one of the top most impediment to realize benefits of agile like flexibility, collaboration and win-win strategy etc..

    Agile is still a taboo in Marketing, sales, pre-sales, legal and finance functions of service companies. Each of these teams work in independently, and create suboptimal silos. There is a need of a framework which align these support function to enable an agile eco system.

    This discussion is to bring perspectives and thought process related to the support / enabling functions of IT services and ponder on creating flow based approach, with each functions working to create a great agile experience to customer