As with most services firm, the number of domains that a company caters to is ever increasing. 

In this session, participants would be introduced to ways of abstracting key processes, procedures and techniques that will allow organizations to adapt effectively with changing domains in their engagements.

Embibing  hybrid concepts, we will explore case studies and relevant scenarios to help Agilists be at their effective best at projects spanning multiple domains. 

 
1 favorite thumb_down thumb_up 19 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Problem Statement

Solution Exploration

Fitment

Conclusion

Learning Outcome

- Domain Agnostic Approach to Analysis

- Change dimension assessment

- Practical techniques of involvement in changing engagements

- Many more

Target Audience

Business Analysts, Project Managers, Scrum Masters, Tech Leads

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Deepak Dhananjaya
    By Deepak Dhananjaya  ~  1 year ago
    reply Reply

    Hi Tejus and Prachi,

     Could you please update the proposal with all the responses you have provided for the comments? It would be easy to look at it!

    Deepak

  • Deepak Dhananjaya
    By Deepak Dhananjaya  ~  1 year ago
    reply Reply

    Hi Tejus, could you please elaborate your approach of the talk? This could become an interesting talk, as the need of today's service industry is versatile BAs. It seems to me as a vast topic, hence your approach of the talk would help us get a first set view as audience and its effectiveness.
    Note: Approach means, details of the steps you mentioned in the Process section. Would it have real case studies? techniques? etc..

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Hi Deepak,

      Problem Statement: The talk will focus on about 4-5 key problems the project setup team (i.e BA, PM etc) tackle during the engagement. 

      Solution Exploration: There may be more than one tool that may fit a particular scenario. We will share these tools and techniques, weigh their pros and cons, and help you by providing a rule of thumb sort of guideline when you encounter similar situation yourself.

      We will also be including an illustrated example from our past real life experience structured in similar fashion for you to realize that this is not all talk and no play :)

      Fitment: Pick and chose your weapon of choice. As explained earlier, a real life example that will be shared will help you decide.

      Conclusion: 

      Intention is to engage the audience with 1 mini activity (about 5-10) mins whereby they could experience one of the tools and techniques explained by themselves.

       

      Hope this helps.

  • Joel Tosi
    By Joel Tosi  ~  4 years ago
    reply Reply

    Hi Tejus,
    I'm having a difficult time relating to your session. Could you provide me with an example so that I could better understand it?

    Thanks much,
    Joel

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Hey Joel,

      This session is aimed at roles who operate in a multi-domain setup. A possible example of what will get covered would be suppose you were a BA in a services firm working in the travel domain, and suddenly you need to go and start an engagement with an Insurance domain customer, this session will talk about certain core processes, activities, and possible tools that would be relevant across any domain. There may be more suitable solutions to a particular situation whereby you may need to do a fitment assessment, which is what will be touched upon in the process section.

      Hope this helps!

      T

      • Doc Norton
        By Doc Norton  ~  4 years ago
        reply Reply

        Tejus:

        Without giving it all away, could you share some of the core processes, ativities, and possible tools that would be relevant across any domain? I'm trying to get a sense of the actual learning outcomes.

        - Doc

         

        • Deepak Dhananjaya
          By Deepak Dhananjaya  ~  1 year ago
          reply Reply

          Adding to Doc's question, are you refering activities to involve like "Reading about the domain, interacting with domain people, etc", i m stating an example, are they similar to what I mentioned? 

          • Prachi Tiwari
            By Prachi Tiwari  ~  4 years ago
            reply Reply

            Hi Deepak,

            While reading about domain and interactions are required, our session will be focussing more on the techniques mentioned in my previous comment.

            -Prachi

        • Prachi Tiwari
          By Prachi Tiwari  ~  4 years ago
          reply Reply

          Hi Doc,

          Our entire session is focussed on domain agnostic techniques. Some of the techniques we will talk about as tools for the adaptive analysis are story maps, empathy maps, IGOE technique, business model canvas etc.

          -Prachi

           

  • steve ropa
    By steve ropa  ~  4 years ago
    reply Reply

    Something that would help me decide if this were a talk I would want to attend is a little more about how this applies to Agile. More specifically, how will it help me or my organization become more agile.

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Steve,

      The tools and techniques intended to be discussed during solution exploration should help your team (and therefore the organization) become leaner when it comes to requirement elicitation and getting the most out of the airtime you may get with your customers.

      For eg. Effort estimation and sizing is an ongoing pain when it comes to project management. Couple this with a lo-fi prototyping idea to give your team a great headstart is one way how I would see as a takeway from this session.

       

      • Joel Tosi
        By Joel Tosi  ~  4 years ago
        reply Reply

        Hi Tejus,

          Were lo-fi prototyping some of the tools and techniques you were going to cover?  If so, could you please elaborate on the rest of the tools / techniques.  That would help me out greatly.

         

        Best,

        Joel

        • Prachi Tiwari
          By Prachi Tiwari  ~  4 years ago
          reply Reply

          Hi Joel,

           

          Yes, lo-fi protyping was one of the techniques, we would be covering. Some of the other tools/techniques that we will talk about are: Story maps, Empathy maps, data flow diagrams, User Journeys, Business Model Canvas, IGOE technique etc.

          Regards,

          Prachi

  • Sonik Chopra
    By Sonik Chopra  ~  4 years ago
    reply Reply

    This subject seems quite interesting but I would request you to provide more details on the session. May be some slides or further details will be good.

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Hi Sonik,

      Do reply with a comment if you feel the comments provided for other posts do not answer your queries.

  • Sachin goel
    By Sachin goel  ~  4 years ago
    reply Reply

    Hi - i am under assumption that focus is around the process abstraction and not common tech solutions which are generally covered by frameworks. Can you pls share any feedback from previous delovery of this topic?
    What are the areas/domains where you have seen this "abstraction" working in real life?

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Hi Sachin,

      In my personal experience, the switch from Insurance domain to travel to financial (European Covered Bond to be specific) was fairly seemless and would have been quite a rollercoaster but for some of the domain agnostic approaches.

       

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

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

    • Tejus Datta
      By Tejus Datta  ~  4 years ago
      reply Reply

      Sorry, but didnt get any alerts about the comments earlier. Just happened to see them today.