The other side of Agile - What can we learn from it?

We all know how paramount collaboration and communication is among members for success in the Agile world. People, Process and Tools are the three pillars of any organization. This session will focus on the people aspect of Agile. Teams are made of people who come together to work on a project from their diverse backgrounds - each of whom bring with them their respective personalities which has developed and evolved over time. According to the Myers-Briggs indicator, there are 16 personality types and each personality type has its own pros and cons. An organization’s success is largely dependent on its team’s personality which in turn is driven by the personality of each and every team member. In this session we will explore questions like – What has personalities to do with Agile? Why do we care? What is the impact of personalities on an organization’s success? Which type of personalities promotes team members to thrive? Which personalities create bully behavior in the team and toxicity in the organization? Can personalities evolve over time?

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

Outline/structure of the Session

Introduction -- 5 min. Understanding personalities, characteristic traits -- 10 min Approach to handle Toxicity, Bully behavior -- 10 min Strategy for effective collaboration -- 10 min. Wrap Up/Questions -- 10 min.

Learning Outcome

Agile aims at open collaboration but no one is taught to be an effective collaborator. This session will ignite an understanding of how to manage difficult situations within the team and provide strategy to effective handle them.

Target Audience

Anyone who collaborates with other people to get the job done

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

    • Michael Peter
      Michael Peter
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      Agile methods help to build a repeatable and reliable pipeline of working code to production. Unfortunately, complex enterprises, including the US government, consider agile the solution to finding and solving all their copious and complex problem. In this space, agile alone is not enough. Reliable enterprise problem-finding and solution-creation techniques aren't yet embedded in the agile toolkit, but nonetheless that's the toolkit brought to bear on critical, complex organization-spanning issues. Typical problem/solution methods can create a local optimization (look at this great thing the team delivered!) but create a global failure (the team didn't consider the other systems and teams involved in the process, and broke them). This is the norm, not the exception, and why large project solutions are typically "meh", not "wow". Given agile is now the de facto approach, now is the time to focus on being exceptional.

      In this talk, we'll cover three years of the fight to achieve agile success on a critical project at the Department of Veterans Affairs: the struggle to enable an agile environment and the realization of what agile at scale REALLY means; the tactical and strategic efforts to identify the fundamental, success-blocking problems of the enterprise, and how to solve them; and what it takes, from discovery, analysis/design, code/test, and release to production, to deliver actual value, and not just "working code."

    • Liked Katy Saulpaugh
      keyboard_arrow_down

      The Agile Reorg: A Survival Guide

      Katy Saulpaugh
      Katy Saulpaugh
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      Reorganizations are notorious for being "a wonderful method for creating the illusion of progress while producing confusion, inefficiency, and demoralization" (credit to Charlton Ogburn). Yet in many cases they are necessary to create the cross-functional, self-organizing teams that succeed the most with the agile mindset. Because reorgs are so painful, many teams and organizations are reluctant to look at team structure at all, and the agile journey is over before it even begins. The result? Organizations and teams are siloed, hierarchical, and process-heavy. If an organization is structured right, it can create fertile ground for a truly agile enterprise. This talk will outline how to approach reorgs for agile teams and minimize the pain using change management techniques.

       

    • Sumedha Ganjoo
      Sumedha Ganjoo
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Scrum is a project management framework and does not specify a set of how-tos or checklists that some other development processes define. Since Scrum can be implemented in various ways, it is easy—and often common—to misinterpret Scrum’s guidelines and make mistakes while implementing it. A new team, in their eagerness to “go agile” and adopt Scrum, often succumb to common pitfalls. Being aware of these mistakes is the first step toward avoiding or resolving them. Sumedha Ganjoo discusses and shares examples of some common mistakes that she notices new teams making. Examples include shared and unclear Scrum roles, excessive estimation, accumulating technical debt, failing to capture non-functional requirements including quality, and not having an effective retrospective. Scrum offers the opportunity to incorporate feedback iteratively, and watching out for these mistakes enables us to deal with them sooner. Learn about these mistakes, review your processes, and determine if you can improve the way your team does Scrum.

    • Liked Chris Murman
      keyboard_arrow_down

      Things Are Broken: A Case Study In Moving Tooooooooo Fast

      Chris Murman
      Chris Murman
      schedule 1 year ago
      Sold Out!
      45 mins
      Case Study
      Intermediate

      “Move fast and break things.” — Mark Zuckerberg

      Mobile is no longer a hobby for companies. In that world, speed is the key. My company embraced the principle of “welcoming changing requirements, even late in development.” It’s allowed us to grow, and we have accomplished some amazing things.

      It’s also caused some challenges for teams. They felt the pain of this pace, and our clients were frustrated by delayed releases.

      This presentation describes a 3-month case study I ran to measure things like team communication, productivity, and quality while implementing Scrum for the first time. The results were convincing, and allowed us to learn what happens when you value speed more than anything else.

      I hope you’ll join me in seeing how we learned to work smarter instead of harder.

    • Liked Scott Blacker
      keyboard_arrow_down

      Help! My Teams are Agile but my Execs are Waterfall!

      Scott Blacker
      Scott Blacker
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Organizations in the midst of a bottoms-up agile transformation can find themselves in a quandary. Even though some (or even all) teams may have adopted agile at the developer / program level, PMOs are often still required to plan, resource, and report on progress with almost no consideration given to the methodologies of the underlying work. 

    • Liked Rupesh Kumar
      keyboard_arrow_down

      Don't fall victim to "if it ain't broke, don't fix it" - Be the change

      Rupesh Kumar
      Rupesh Kumar
      schedule 1 year ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Have you ever imagined how our ancestors built Stonehenge, the Great Wall of China and the Pyramids without the tools and technology that are available to us today? Now imagine today’s world without the internet, smart phones and technology. What do you see? I see that there have been generations before us and there will be generations after us which will develop ways to survive, excel, and perish. One thing that is constant is change. Most of the organizations today acknowledge that change is good and have discussed it in great detail; however, but fall short in realizing the change.

      Change is an absolute truth. No one can agree with this more than organizations in today’s cut-throat competition, where constant change is the norm for their survival. Organizations which are slow to respond to change or resist change are on the verge of being obsolete. They need to change for various reasons such as external competition, market pressure, performance issues, changing workplace demographics, globalization etc. Organizations which invest in proactively responding to change are more likely to not only survive or but also emerge as leaders, creating new markets which never existed before. When organizations are successful, they become complacent and continue to do what worked, but in doing so you keep getting what you were getting; where is the growth in that? The main reason for organizations to resist change is in their mindset; change is perceived as negative or with skepticism. How many times have we heard the phrase “if it ain't broke, don't fix it.” Many organizations have fallen victim to this mindset and have become extinct.

    • Liked Rupesh Kumar
      keyboard_arrow_down

      How Scientific Method complements Business Value? - Lets take a look

      Rupesh Kumar
      Rupesh Kumar
      schedule 1 year ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Product owner provide requirements and its business value to IT which in turn works on building a solution. Usually the focus is geared towards building the correct solution based on customer’s requirements. But can we guarantee if the requirement and the business value provided by the customer is right? Does the product owner really know if their requirement adds value? We propose a shift in how the requirements should be processed. Instead of accepting requirements based on business value and customer’s need, we suggest a scientific method of evaluating a requirement to see if it really does add any value prior to adding it to the backlog. Most of us in our early school years might have studied in science the scientific method for asking and solving a scientific question.