Agile Business Analysis Anti-Patterns

In this talk we will pick up various (5-7) business analysis anti-patterns, specially for Agile projects, that either we ourself have practiced at some point of our BA carrier or have seen other BA's doing. We will talk about the symptoms which act as a sign of presence of these anti patterns, why are the problems associated with them and what are the ways to get rid of them.

These anti-patterns may range from behavior with customers to behavior with the own team.

Some of the anti-patterns we are planning to discuss:

1) BA aka The Order takers
2) Task (UI/backend) based stories
3) Engrossed in too much detail to miss the view of bigger picture - story verus feature 
4) As a “user”...., where the user is either "system" or "product owner"
5) Leave the NFRs / CFRs to the Developers/Tech lead
6) Detail the hell out of stories
7) Focus on Happy Paths only
8) Focus on building a software over solving the real problem
9) Resist change in requirements

 

 

 
3 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

1) General Introduction about Business Analysis (5 mins)

2) Discuss 7 Business Analysis Anti-patterns (7*5 mins)

3) QnA

Learning Outcome

Learnings the we would like participants to take away from the session are:

  1. What Symptoms to watch out for when doing analysis on agile projects
  2. What harm these anti-patterns can cause to the team/project
  3. What are some of the underlying cause of occurrence/practice of these anti-patterns
  4. What are the possible solutions or how to shun or evade these anti-pattern

Target Audience

Anyone who is part of an Agile Team

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Pramod Sadalage
    By Pramod Sadalage  ~  3 years ago
    reply Reply

    Unnat,

    Would it be possible for you to list the Anti-Patterns?

    Tell us how you are going to build a story around the presentation?

    do you have a slide deck you can share?

     

    Thanks

    • Unnat Gupta
      By Unnat Gupta  ~  3 years ago
      reply Reply

      Hi Pramod,

      We have not finalized the 7 we will pick up, though we have compiled a list of 9 as of now and looking to add more and then pick the 7 which we think are the most common

      1) BA aka The Order takers

      2) Task (UI/backend) based stories 

      3) Engrossed in too much detail to miss the bigger picture view 

      4) As a “user”...., where the user is either "system" or "product owner" 

      5) Leave the NFRs / CFRs to the Developers/Tech lead

      6) Detail the hell out of stories

      7) Focus on Happy Paths only

      8) Focus on building a software over solving the real problem

      9) Resist change in requirements

       

      • Pramod Sadalage
        By Pramod Sadalage  ~  3 years ago
        reply Reply

        Unnat,

        Would you mind updating the proposal with this list. Also mention in the proposal how you plan to give background and context and lessons learnt around each of those.

        If you have a in progress deck, do you mind sharing it with the review team?

         

        Thanks


  • Liked Alexey Ilyichev
    keyboard_arrow_down

    Alexey Ilyichev - Skype goes agile: don't repeat our mistakes

    Alexey Ilyichev
    Alexey Ilyichev
    Agile Coach
    ScrumTrek
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In 2011, I worked for Qik, a startup that got aqcuired by Skype. At that time Skype was in the middle of an agile transition. Аfter aquisition, Qik team was told to adopt the Agile process used by Skype. I worked with the team as an agile coach. After adopting Skype's "agile" process, our ability to deliver was brought down to almost zero. In this talk, I'll tell you the story as it happened, analyze the key problems that we faced and describe how we finally solved them. Come to this talk, if you want to avoid similar mistakes. If you are already through with your transition, I would be interested to know if you see any patterns. 

  • Liked Sunil Mundra
    keyboard_arrow_down

    Sunil Mundra - Getting A Partner To Adopt Agile

    Sunil Mundra
    Sunil Mundra
    Principal Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Intermediate

    Due to the business benefits which accrue from Agile, clients are demanding their IT Departments/Partners to adopt Agile. It is quite common to find a situation where the client has adopted Agile, but its Partner/Vendor has not.


    This talk is based on my consulting engagement with a client who had adopted Agile and their partner had not, and the client wanted the partner to Adopt Agile.


    The talk will cover the critical challenges encountered in getting the partner to adopt Agile, especially given the wide difference in cultures of both organizations and also the organizations being located in different continents. The talk will also cover the key learnings from this journey.

  • Liked Shirish Padalkar
    keyboard_arrow_down

    Shirish Padalkar - Application Security - The Agile Way

    Shirish Padalkar
    Shirish Padalkar
    Senior Consultant
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Traditionally application security has involved upfront design and a big bang penetration test after development. This leads to the phenomenon of “bolt-on” security that translates into increased cost and complexity.

    Drawing on our experience on real-world projects, we show how security can be baked-in on an agile project. Using case studies we demonstrate how security concerns are captured during project inceptions, how developers write secure code, security testing is automated and how configuration management can help achieve secure deployments. This talk introduces several new concepts like secure by design, secure design patterns and lightweight code reviews.

  • Liked Sudipta Lahiri
    keyboard_arrow_down

    Sudipta Lahiri - 10 (Understated) Lessons from TPS!

    45 mins
    Talk
    Intermediate

    I talk about 10 lessons from Toyota Production System that are important but not talked about.

    Lesson I: Getting the foundation right!

    Lesson II: Be patient to get the foundation right!

    Lesson III: 3S vs 2S

    Lesson IV: Three stages of Seiso

    Lesson V: Understanding Seiketsu

    Lesson VI: Implementing Shitsuke

    Lesson VII: Improvement initiatives are harder to sustain

    Lesson VIII: Keep broadcasting your success

    Lesson IX: Kaizen vs Sustenance

    Lesson X: Lessons from 3MUs and Visual Management

     

  • Liked Anand Bagmar
    keyboard_arrow_down

    Anand Bagmar - The Agile “Chalta-Hai (It’s OK)” Manifesto

    Anand Bagmar
    Anand Bagmar
    Director - Quality
    Vuclip Inc.
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    The Agile Manifesto was formulated by 17 people in 2001. We know the principles of the Agile Manifesto … but do we really understand it?

    Depending on the organisation culture, the team culture and various other factors, they reach varying levels of Agile adoption. Martin Fowler talks about the levels of adoption and the path to get better via his post on “Your Path through Agile Fluency”.

    Not surprisingly, not all Agile project implementations are successful.

    This session is going to take you through a journey to talk about some of the Myths of Agile and also behaviors that inhibit organisations and teams to reach great(er) heights in Agile Fluency to achieve Agile’s benefits.  As a result, the Agile Manifesto has remained on paper, but teams have come up with their own ‘workarounds’ - which are not truly solutions to solve a complex problem well.

    We accept it because of our “chalta-hai (it’s ok)" attitude. At the end, what are we then left with? The Agile “Chalta-Hai (It's OK)” Manifesto.

  • Anand Bagmar
    Anand Bagmar
    Director - Quality
    Vuclip Inc.
    schedule 3 years ago
    Sold Out!
    90 mins
    Case Study
    Intermediate

    The key objectives of Organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
    In such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury!

    There are various practices that Organizations and Enterprises need to implement to enable CD. Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful.

    Testing in Organizations on the CD journey is tricky and requires a lot of discipline, rigor and hard work. In Enterprises, the Testing complexity and challenges increase exponentially.

    In this session, I am sharing my vision of the Test Strategy required to make successful the journey of an Enterprise on the path of implementing CD.

  • Liked Yilmaz Guleryuz
    keyboard_arrow_down

    Yilmaz Guleryuz - Fibonacci Pairing: Learning through Collaboration

    Yilmaz Guleryuz
    Yilmaz Guleryuz
    incognito
    WareNinja
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    According to many researches, we learn the best when we experience it personally, and we comprehend when we teach to someone else.

    So if you want to achieve ample understanding of a topic, you’ll need to follow these basic steps:

    "Listen -> Observe -> Do -> Share"

     

    Pair-programming is a well-known practice, and it has been introduced by one of the thought leaders of Agile world, Kent Beck. I respect any technique that encourages collaboration and interaction among teams, and gets teams to communicate better.

    However, if you want to establish understanding of mastery or a skill-set, and increase the shared knowledge across your team members, then you need to re-think & apply new techniques.

    In this talk, I’ll share about What-Why-How of "Fibonacci Pairing" technique, which is yet another discovery from practice.

    The main goal of that technique is to establish understanding and improve collaboration, without overcrowding by artificial ways like lecturing.

    Fibonacci Pairing is simple yet very effective technique that can improve team work. This technique should be regarded as a complementary way to improve team culture effectively.

    We will elaborate with practical examples, real life experiences, and applicable ways onto different contexts.

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - Agile Project Forecasting with Focus Factor

    Vishal Prasad
    Vishal Prasad
    Project Manager
    Springer Nature
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    How many deliverables should we commit to our customers in, say, the next two weeks? An intriguing question asked by many Agile teams at the beginning of every iteration. The answer to this question depends largely on the team's thinking, philosophy, and skills -- which unfortunately cannot be measured. Then how do we forecast the deliverables?

    How about a mathematical formula that provides an unbiased control based on the historical achievements of the team, which can be used for prediction? That's exactly what focus factor does.

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta - Calculating RoI on Agile Enablement

    45 mins
    Talk
    Advanced

    "We want to be Agile!!...

    Why?

    Because its cool, and its becoming a norm, it will help us to cope with changing requirements, help us deliver faster etc etc."

    Isn't this a common sentiment in organizations struggling with the ever changing user/customer taste?

     

    With Agile going main-stream with most organizations looking to have at least a few business critical projects run in an Agile way, the question of ROI comes up. Shifting from a traditional way of building software to an Agile way, requires change and as any good business leader would know; change is not free. Business leaders would like to understand and justify the return on Investment to make this shift. In our talk, we will be talking about how to look at the Agile process holistically and how this process affects budgeting and how early value realization can help offset the cost of change. We will also discuss stories of other in house IT shops and product houses who have made this shift and the journey they have undertaken

    From our experience of working with such organizations, we have found that for these process-focused Agile adopters, much of their measurements include:

     

    - how long is our stand-up?

    - how long is our build?

    - how many stories do we have?

    - how many points can we fit into a sprint? etc.

     

    From their perspective, they already have plenty of metrics. Often it's also the case that they're getting benefit, just because common sense does kick in behind the scenes, and because they're delivering more frequently as a result in the reduction of documentation, so they don't always run out of money either. That leads to bad habits, possibly, rewarding wrong practices. In this talk we want to discuss metrics we have used on the projects and have found useful. Metrics like: Cycle Time, Time to market (also called Lead Time), Collaboration, Quality (in terms of code complexity , code coverage, test pyramid) and bus factor. One thing to note is that any of these metrics alone would not provide holistic way of measuring benefit, and hence a combination of them is required.

     

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta - Know Your MVP!!

    45 mins
    Talk
    Intermediate

    MVP is defined as : "that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."It doesn't say a thing about the product being valuable to the customers or market segment.

    MVP is minimum viable product *NOT*  minimally marketable feature set / first release!  MVPs are the experiments we learned from on the way to our first release of the software.

    To us the core of the difference between "Minimally Viable Product" and "Minimally Marketable Product" is in the purpose.  An MVP's purpose is to learn, an MMP's purpose is to serve.  Understand the problem vs address the problem.

     

  • Liked Unnat Gupta
    keyboard_arrow_down

    Unnat Gupta - Prioritization Techniques: Lets move beyond MoSCoW!!

    90 mins
    Workshop
    Intermediate
    • Have you been in a situation where everything gets prioritized as MUST HAVE?
    • Have you been in a situation where you have find it difficult to get different stake holders to agree on relative priority of different features?
    • Most of the time is spent in discussiing low value features?
    • Whoever screams the loudest, gets their pet features prioritixed high?
    • Do you want to learn some more prioritization games/techniques that can be used to start prioritizing at Feature level and subsequently refine it to story level?
    • You feel the current technique(s) you use for prioritization are time consuming and ineffective?

    If answer to any of the above questions is yes, this is the workshop for you to attend

    Why Prioritization?

    Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product. In reality, customer expectations are high, timelines are short, and resources are limited. Any project with resource limitations has to establish the relative priorities of the requested features, use cases, or functional requirements. Prioritization helps the project manager resolve conflicts, plan for staged deliveries, and make the necessary trade-off decisions. Thus, requirement prioritization is used in Software development for determining which requirements of the software product/application should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first.

    Several methods for assessing a prioritization of software requirements exist. In this workshop we are going show some of techniques/games we have used for feature prioritization.

     

  • Liked Sarabjit Singh Bakshi
    keyboard_arrow_down

    Sarabjit Singh Bakshi - Art of Processing People in batches - Lets Re-factor our Schools

    45 mins
    Talk
    Intermediate

    My talk will be highlighted on the currrent Education System and how Agile and Lean Mechanisms can help us refcator our education System . As we all proceed in this digital world its important to understand what extra can we do to make our children education more informative and creative . Using Agile and Lean from Gurukuls to Modern school- what do we think -Is the current education system is helping our students . Would like to give an insight on where are we going how we can improve it and how we all can contribute to make it better. We can talk on using Agile as Change Agent towards transforming the way our children precieve learning. 

  • Liked Ajay Avinash Solanki
    keyboard_arrow_down

    Ajay Avinash Solanki - Agile Coaching - Giving and Receiving Feedback

    90 mins
    Workshop
    Advanced

    Agile is based on crossfunctional and self organizing teams. Agile is based on the Plan, Do, Review and Adapt Feedback Loop. Feedback is the basis of Agile. Feedback can be amongst team members, between Scrum master and the team, Product owner and Scrum Master, Stakeholders and Product Owner and various combination of the same. We generally give a deficit based feedback. We point out to the short commings, mistakes, fix blames etc. This is a very emotionally chaged discussion which leads to a lose lose situation and a bad relationship. Contrary to this Giving feedback should be based on strengths. It is a planned approach which has to be rehearsed before hand. The main objective of giving the feedback is to find out solution instead of fixing the blame. Let us learn the techniques by which this can be made possible.

  • Liked U S VINEESH
    keyboard_arrow_down

    U S VINEESH - Agility lessons from Nature

    45 mins
    Talk
    Intermediate

    When Darwin said “fittest,” Darwin did not mean strongest or fastest or even smartest: he meant most adaptable, best at handling change.

    Ants have existed close to more than 100 million years now and they can be considered as one of the most flourishing beings on our earth. They have colonized almost every landmass and they thrive in most ecosystems. Have you ever wondered what makes them so successful?

    This success of theirs in so many environments has been attributed to their social organisation and their ability to modify habitats, tap resources, and defend themselves. Ants are one among the most agile creatures that we have seen till date.

  • Liked Nilotpal Das
    keyboard_arrow_down

    Nilotpal Das - Head First Agile and Organizational Transformation

    45 mins
    Experience Report
    Intermediate

    This is a collection of real time case studies of failed projects. It is an autopsy of these failed projects studying why these projects failed and how application of agie principles could have saved them.

    It is also a study into the organizational culture, behavioral attributes and the people issues and how agile addresses them.

    And finally it is a study of why doing a few projects with agile is not sufficient. How complete organizational transformation into agile practices is necessary for long term success for projects, processes and people.

  • Liked Geeta
    keyboard_arrow_down

    Geeta - Chicken Soup for the Agile Soul

    45 mins
    Experience Report
    Intermediate

    Going by the adage - "Without struggle, there can be no progress", we intend to share some extraordinary stories that have and can change the way we work and interact in the Agile space. Every team, whether Agile or not, goes through the forming, storming, norming and performing stage. The storming phase is when an Agile team can look inwards using some Agile best practices to tide over the storm. The pressing challenges that a team can face during the storming phase can be categorized into:
    1. People
    2. Process
    3. Technology

    Through our talk, we would like to share some specific challenges that we faced in each of the above categories and how we overcame them -

    =================================================================================

    Example for people:

    Anti-Pattern / Challenge : In a distributed environment, code got overwritten in spite of an existing version control tool
    Conclusion : Better self organization within the team
    Resolution : Cross pollination, face to face communication, automated notifications
    =================================================================================

    Example for process :

    Anti Pattern / Challenge : Team got together to solve a problem and very little got accomplished due to external dependencies
    Conclusion : The need for more collaboration and the right problem solving protocol
    Resolution : Adopted design thinking, created cross functional teams, applied 'Pareto' principle
    =================================================================================
    Example for technology :

    Anti Pattern / Challenge : Different deployment scenarios and technology choices
    Conclusion : The need for continuous and collaborative integration
    Resolution : Created an inhouse one click seamless deployment tool named 'Deployer'
    =================================================================================

    Today as a team we have expanded beyond the bookshelf, matured as agile practitioners. And now we’re working hard on a creating a visionary path. Improving the Agile world around us is part of our mission of learning, sharing and growing. The talk will re-emphasize our journey through agility and constant evolution.

     

  • Liked Pankaj Kanchankar
    keyboard_arrow_down

    Pankaj Kanchankar - Line Managers - an Endangered Species in Agile

    Pankaj Kanchankar
    Pankaj Kanchankar
    Agile Coach
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The matrix organization of yore relied on maximizing returns on each skillset. This lead to having line managers and practice horizontals.
    Engineering managers looking after developers and practice managers looking after the respective practices of BA, QA and PMO. This lead to having multiple lines of reporting for team member whilst on the project.
    In Agile teams, focus is on the self organising teams of empowered employees working towards common success criteria (project success is team success). Not everyone can be a PO or a Scrum Master. So is the role of so called line managers or practice managers become redundant?
    Whats their role in the agile teams?
    How their role needs to transform

    In this talk I will be addressing these questions. Bring out how some of their responsibilities are now taken up by the team or Product Owner or Scrum Master. I will also be suggesting how line managers can take this as an opportunity to morph into more meaningful roles that help the organization and teams. 


  • Liked Jisha Sharma
    keyboard_arrow_down

    Jisha Sharma - People Dynamics – Agility to our Rescue

    45 mins
    Experience Report
    Intermediate

    We (Jyoti and I) believe Agility is the mindset that makes you successful by doing what makes sense at any given point. Success in IT projects comes from not only following the mechanics but also applying your skills to people dynamics.

    We plan to talk about our experience where agility has helped us fight back in difficult situations than take a flight back. 

    Key topics

    People dynamics - 

    1. Flexing our styles
    2. UX at the center - Personas, Euro/Rs/Dollar test, MoSCow
    3. Workcell
    4. Big picture
    5. Customer shoes

    Agile Mechanics -

    1. Quantify priority
    2. Deliver in sprint 0 too
    3. Risk burndown

    Experience sharing

    1. Varied experiences 
  • Liked Jagadeesh Balakrishnan
    keyboard_arrow_down

    Jagadeesh Balakrishnan - “Agile Project Management – Is it an Oxymoron?”

    45 mins
    Talk
    Intermediate

    Often than not, project management is perceived to be an administrative activity giving rise to lengthy documentation and clear “to do” instructions to the team. On the contrary, Agile is proclaimed to be the new, trendy Avatar proclaiming less or sometimes nil processes to follow and having a “Do it yourself (DIY)” team culture! What the untrained eye misses to see is a fine balance that connects project management philosophy with agile values. This talk will focus on demystifying the art of Agile project management by raising common questions relating “Agile” & “Project Management” and by providing answers that result in a successful marriage of the two.

    The talk is delivered based on the experience gained by working with Singapore clients embarking on agile and also as a result of experimenting agile ideas in the Master of Technology class with Software Engineering students.

  • Liked Sridharan Vembu
    keyboard_arrow_down

    Sridharan Vembu - Relevance of the '12 principles' through project lifecycle - A Practitioner's View

    45 mins
    Case Study
    Intermediate

    This talk is about taking a closer look at how one or more of the 12 principles behind Agile Manifesto are closely connected to the different stages of the project lifecycle and how they impact the right choice of practices and tools at each stage. 

    Few sample scenarios: 

    1. Major change in the way iteration planning was done - common backlog for the platform (comprising of different application teams), think each 'iteration' as a 'release' - deployment of business features to production end of each iteration - resulted in greater collaboration, no separate integration/stabilization phase towards major commercial launch

    Relevant Principle: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale

    2. Reflecting on team organization - one large team (or) multiple smaller teams and / or feature teams, concepts like Mountaineers-Divers, Navigators-Drivers -> effective and easy context sharing, no stepping-into-each-others-shoes, efficient balance between big picture view and attention to details and such.       

    Relevant Principle: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly 

    3. Feature kick-offs, analysis volleyballs, need basis Dev/QA/BA huddles, vide calls with distributed teams, subject-specific-google-hangouts -> Effective communication and fewer email conversations  

    Relevant Principle: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation

    Experience clearly suggests that following the right principle at the right time for a specific situation ensures successful outcome, while ignoring one or many of these principles often results in failure.

    4. Adverse effects of measuring the delivery team's efficiency of the team one-dimensionally based on the Story Points delivered

    Relevant Principle: Working software is the primary measure of progress.

     

    In this talk, through specific practical examples, I would be explaining

     - identifying the right principles for each life cycle stage of the project/program

     - deriving the right practices based on the principles and following them effectively to deliver value to customer 

     - business and delivery constraints that prevented us from adhering to some of these principles, resulting in not-so-desired outcomes

    In summary, I would like to emphasis the importance and relevance of the 12 Agile Software Principles behind Agile Manifesto in everyday life of a Agile Practitioner.