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

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.

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

Outline/structure of the Session

Introduction -- 5 min.

Business value - Do we understand it?  -- 10 min

Scientific method  -- 10 min

Scientific method and Business Value, a recipe for success  -- 10 min.

Wrap Up/Questions -- 10 min.

Learning Outcome

In this session we will discuss how to use the scientific method in Agile software development, by framing a requirement as a question and then performing background research for proving a hypothesis driven by dependent and independent variables, the control and the constants. We will also look at the what and how to gather materials and conduct experiment and finally record and analyze the data prior to drawing conclusion and communicating the results to the customer.

Target Audience

Any IT and Business Personnel

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

    • Liked David Horowitz
      keyboard_arrow_down

      The 7 Secrets of Highly Effective Retrospectives

      David Horowitz
      David Horowitz
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      Retrospectives are the core of agility. And yet they are the scrum ceremony that is most frequently skipped. Many teams like the idea of the retrospective but find them boring, or worse ineffective.

      This talk aims to re-energize retrospective facilitators and participants. Starting with the basics: "what's a retrospective and how do you run one?", this talk reveals 7 secrets that lead to more engaging, more effective retrospectives.

      You'll learn:

      * The best way to ensure your retrospectives lead to real change

      * The "pledge" everyone on your team should take before participating

      * How to know who to include in each retrospective

      * The single most important thing you can do to keep your team engaged during the retro

      * And much, much more!

    • Liked Jim Damato
      keyboard_arrow_down

      Business Agility - Being the Bigger Dog in a Dog Eat Dog World (Even for a Chihuahua!)

      Jim Damato
      Jim Damato
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Advanced

      Business is tough. If your market is any good, other companies want your revenue and market share. A lot comes your way that's beyond your control, so how do you stay competitive in a dog eat dog world? You strive for Business Agility.

      Business Agility is about being able to sense, create and respond to change, quickly and confidently. Every organization has the bravado to think they do, but few actually can. Think about these local companies who are:

      • At the top end of the market being threatened by a newer, faster rival.
      • Experiencing a market shift threatening half their revenue.
      • Subject to whims of powerful regulation. 
      • New in an emerging market and need to stay ahead of the major players. 

      Major change can come from all angles, whether from competitors, regulators or market shifts. Companies need to be able to execute not just at the execution level, not just as the portfolio level, but at the business level, so they can handle the change or better yet, BE the change.

      Business Agility isn't about how big you are, it's about survival of the fittest. Whether you are a small business or a publicly traded company, be the bigger dog.

    • 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 Ben Morris
      keyboard_arrow_down

      DevOps for the Rest of Us, Reprise

      Ben Morris
      Ben Morris
      Chris Cassatt
      Chris Cassatt
      schedule 11 months ago
      Sold Out!
      45 mins
      Demonstration
      Beginner

      (This talk was well-received in 2015, so we can do an updated version for 2016)

      DevOps as a buzzword is gaining traction, but what does it really mean? Managers, non-techies, and developers-new-to-devops will get a guided demo of development automation. See all the cool tools in action - continuous integration, automated testing, cloud deployment, etc. More importantly, we'll walk through what they do, and why that adds value to a project. 

      This talk will...

      • Break down the buzzwords and define some key technical practices in plain english.
      • Uncover the pain that leads teams to seek greater automation.
      • Demonstrate a continuous integration pipeline working in practice via live demo.
      • Diminish the knowledge gap between technical practitioners and managers/analysts/coaches.
      • Level-up the vocabulary of non-technical attendees.
      • Introduce practices to developers who don't yet work in an automated environment.
      • Spark "ah-ha" moments to convert skeptics into DevOps believers!

      By the way, all of the tools in the demo are some combination of free and/or open source. DevOps doesn't have to cost a lot.

    • 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 Ken Furlong
      keyboard_arrow_down

      What is an Agile Coach?

      Ken Furlong
      Ken Furlong
      schedule 11 months ago
      Sold Out!
      90 mins
      Talk
      Intermediate

      What does an Agile Coach do anyway?  We already have Scrum Masters, why do we need a coach also?  We have only a few teams or perhaps just a single team; isn’t an Agile Coach a lot of overhead?

       These are excellent questions asked by many organizations and individuals.  They deserve good answers.

       In this talk, we’ll provide those answers and discuss how Agile Coaches can have a huge multiplier effect for any organization striving to transform, execute, or improve.  We’ll cover coaching both at an abstract level as well as the nuts-and-bolts day-to-day level.  Participants will leave with an understanding of what an Agile Coach can do for them and how to explain to others why their organization should have one.

    • Liked Joey Spooner
      keyboard_arrow_down

      Using Kanban to measure and improve your team’s performance

      Joey Spooner
      Joey Spooner
      schedule 11 months ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Are you lazy like me and want a simple way to measure your team’s performance? The Kanban Method, which is sometimes referred to as the "Start with what you do now" approach to evolutionary change, offers a simple and easy way to start measuring and improving your team’s performance.

      I will take you on a brief journey through three government teams that are using Kanban to define, measure, and improve their performance as well as their processes and quality of work. Throughout this talk, I will explain what Kanban is, show three different approaches I have used when implementing a Kanban system, help you know when your Kanban system is predictable and when it is not, and provide simple steps so you can start your Kanban efforts the next day.

    • 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

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

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

      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?