The SCRUM and the willpower: how neuroscience can boost your productivity

Willpower is the force that is between the brain activity (I want to do this or I need to do this) and the action itself (start coding). If there is not enough willpower, people find it difficult to start any activity (especially that involves
decision making).


What is the standard approach when you feel tired and find it difficult to concentrate? Take some coffee (but latest research shows that coffee depletes the brain activity, even when body has more energy), take some sweets (but sugar ends quickly and gives even more exhaustion to the body)? These widely used strategies generally do not work, and in long-term even add harm to the body and brain.


The willpower is not endless (so-called muscle theory of willpower), it can be saved, it can be trained, there are approaches how to keep the willpower level high. To keep the willpower (and thus, productivity) on the high level, people should know and use different approaches that lay in the field on the social and cognitive science.


There are a lot of evidences that SCRUM improves the developer’s productivity in terms of speed of development, code quality, and accuracy of design. Unfortunately mainly all recommendations from SCRUM coaches look like “believe me, if you do this, you will have better velocity”. Yes, it works. But why does it work?


Sometimes SCRUM does not give such great results even when main elements are in place. The question “Why” and “What makes the difference” is here again.


I will describe the model of relationship between the willpower related brain metabolism on very low level (specific amino acid cycle) and the SCRUM practices. I can prove that SCRUM addresses the productivity of the people’s brain using 3 different flows simultaneously. There are several tips that make these productivity flows working or not. You can make Agile productive, you can have non-productive Agile. I will show you where the difference is.


Overall there are 10 productivity tips that can be put into 3 flows.


As the outcome of this session, Agile coaches, and all people who can change the process (in fact that is any team member) will review their SCRUM: does the way they have it improve the productivity or they are losing all the power? The changes are cheap, the outcome can be huge.

 
4 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Presentation type - lecture
Introduction: 5 minutes; I am going to describe my background so the audience
understands how I came to this topic and can build the trust. Also here I will
convince people why they may want to look at their productivity and what is expected
from the Agile teams. I will list the types of knowledge involved and warn the
people that this will be quite an intense brain exercise with a lot of new
information and call for action.
The neurological piece: 10 minutes; I plan to go deeper to describe the biological
foundation for the brain productivity and what happens with the brain if there are
not enough proper amino acids.
The productivity piece: 10 minutes; What actions lead to the great brain cognitive
abilities?
The SCRUM and the brain: 10 minutes: I will draw the 3 flows that exist in the SCRUM
process that make the brain work more effectively. For each SCRUM part I will
describe how you can perform it so it boosts the performance and what actions lead
you to normally weak productivity.
Call for action: 5 minutes: Each description will have a call for action: so
everyone can check, do they make SCRUM in Productivity way or in ordinary way. This
makes the lecture more interactive and people will immediately have the personal
outcome, like they do on the training.
Wrap Up: 5 minutes: Questions and answers.

Learning Outcome

Learning outcomes:

As the result of this session people will:
- Create the list of immediate improvements to existing SCRUM process
- Analyze do they use their brain in the productive way or not
- Agile Coaches and Scrum Masters will have new type of arguments when they
are proposing changes

This session is more like a discussion about how to make brain working better, what
the drawbacks are and how the change can be done by everybody. I got very positive
feedback on this topic from local conferences and inside my company. Also this topic
is quite unusual for Agile conferences and will bring a good contrast and variety
with experience reports about using Agile.

Target Audience

Any role, especially Scrum Masters and Agile Coaches are welcome

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Very interesting connection between scrum and neuroscience. Its all about bringing in predictability and rhythm! I am coming to think about if 45 mins is enough as there is a vast set of information you are covering. If thats not enough, see if you would like to pick few of those cncepts and make it more effective! 

     

    • Anna Obukhova
      By Anna Obukhova  ~  4 years ago
      reply Reply

      Hello Deepak

      Thank you for your feedback and improvement suggestion. I tried this topic in 60 and 45 minutes speech and both went good. I agree that there is huge set of information there (usually 1 slide is a whole book or a large concept), but these concepts are well-known.  What I can see is that people are able to catch the idea and if they have questions or desire to know more, the references are available and they always are able to catch me during the conference.

      I would be happy to have 60 minutes slot for this topic, but 90 minutes seem to be too long and people lose the willpower and brain focus))

      Thanks

      Anna

  • Ebin John
    By Ebin John  ~  4 years ago
    reply Reply

    Hi Anna,

    Very interesting topic. I hope you are going to map  In the conference we have Scrum, Kanban, Lean, Scruban enthusiasts. I personally feel that the talk will be more effective if you could accommodate other framework as well (not only scrum).

    - Ebin

    • Anna Obukhova
      By Anna Obukhova  ~  4 years ago
      reply Reply

      Hi Ebin,

      Thank you for considering this topic interesting, I'm also very excited about it.

      Do you have any links/references to the evidence that other than Scrum techniques have hyperproductivity like what Jeff Sutherland found? If yes, please send them to me, I would be happy to include this and investigate what pearts of it may contribute.

      I absolutely agree that all Agile frameworks are brilliant and use several tips that make life and productivity better, I can mention this, bit I see only Scrum that has maximum concentration of these, that is why I used it as an example.

      In any case, knowing what principles are related with the productivity and willpower saving can improve the behaviour and performance in any framework.

      Thanks

      Anna

       

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

    Anna, this is a great topic. Love how you've pitch the whole connection between habits and productivity and blended it with how the brain functions.

    In your talk I see that you are referring a lot to Scrum, but actaully I feel this body of knowledge can actually be applied at process level (like eXtreme Programming which is a super-set of Scrum [framework]. XP has everything Scrum has and many more usefull values, principles and practices beyond it.)

    I knew that L-lysine is a basic building block of protein and it helps convert fatty acids to energy. But I was not aware of its connection with willpower. Is there any research which will help me understand the connection better?

    100% agree with you on "Take one cup of coffee with sugar and that's the worst thing you can do." Some folks refer to it as a "brain-drain" technqiue. A quick way to drain your brain.

    Also you claim that to set something as a habit, you need to do the same exact steps in the same order in the same environment 15 times in a row and hence you need to do something at least for 21 days for it to become a habit. I'm intrigued. Where can I find data to back these numbers?

    You suggest to become hyper productive on needs to do the daily scrum at the same time, same place, in the same order of people and with the same set of questions in the same order. How practical do you think this is?

    • Anna Obukhova
      By Anna Obukhova  ~  4 years ago
      reply Reply

      Hi Naresh,

      Thank you for the interest, answering in the body with [Anna] mark to start the answer.

      Anna, this is a great topic. Love how you've pitch the whole connection between habits and productivity and blended it with how the brain functions.

      [Anna] – Thank you! I love the topic as well and it happened that people who already visited my talks on that, recommend it to their friends on the conferences that I feel very encouraging.

      In your talk I see that you are referring a lot to Scrum, but actaully I feel this body of knowledge can actually be applied at process level (like eXtreme Programming which is a super-set of Scrum [framework]. XP has everything Scrum has and many more usefull values, principles and practices beyond it.)

      [Anna] Yes, I agree that XP, Kanban and other Agile approaches have a lot in similar practices and they all share great success. I’m referring to hyperproductivity in Scrum, which is supported by Jeff Sutherland’s article and set of conference talks that are very well-known and cited, but I don’t have such articles or conference proceedings or my own measures about XP. I would be glad if you can point me to some, I would be happy to improve the presentation adding this. Anyway I can mention during the talk that even if people do not use Scrum, but use these principles, they can expect the productivity increase (and this is perfectly valid from my experience, but just would like to have evidence about this possibly someone will calculate improvement after the presentation?).

      I knew that L-lysine is a basic building block of protein and it helps convert fatty acids to energy. But I was not aware of its connection with willpower. Is there any research which will help me understand the connection better?

      [Anna] – Thank you for touching my favourite topic))) The theory about the connection of Lysine and willpower was created and investigated in 1970s in Russia by War Medicine Academy of Sciences (I think it will never be referenced or googled for security and language reasons, but my coach participated somehow in this research).

      For sure they were looking for the increase of ability of soldiers to keep making decisions and select tough ways in the conditions of stress, fatigue and uncertainty.

      When I heard this, I did secondary research for the Lysine theory and found that it is supported by the modern investigations strongly enough to suggest it worth talking about.

      I’ll explain part of it: The willpower itself means ability to still follow the decision (not selecting easy or habitual way) when brain is fatigued. Brain is selecting habitual way simply because it takes less energy (there is referenced research on that, cited in books). But what is drained? Why willpower is not endless? The western main theory is because of sugar. But the problem is that brain all the time has necessary amount of sugar (if it does not, it will be dead or in seconds, this is pure biology), the only difference is the sugar source. The sugar theory is highly critiques for this fact, but still used and I mention it in my talk. But when there is not enough glucose in the blood (easy source), the body comes to stress and goes to the sugar saving mode. Stress mode is connected with cortisol level, and is followed by fatigue, and brain fog and problems with concentration and short-term memory. And here is the Lysine, it is the molecule that works with cortisol to reduce its levels, and if it is not enough Lysine, the brain does not work well (this was also research by others) and set of other relations. Also with the reference to Lysine, the researchers have found that after flow-condition activities that brain function is still close to the start level, even when the sugar was used a lot (this is what the russian research was about).

      Just if you are interested, I can add the reference list, there are at least 11 books that were used in the preparation and several articles about Lysine.

       

      100% agree with you on "Take one cup of coffee with sugar and that's the worst thing you can do." Some folks refer to it as a "brain-drain" technqiue. A quick way to drain your brain.

      [Anna], thank you, this is quite unique that you agree with that, people mainly try to protect their habits, not trying to understand how them can make life worse)))

      Also you claim that to set something as a habit, you need to do the same exact steps in the same order in the same environment 15 times in a row and hence you need to do something at least for 21 days for it to become a habit. I'm intrigued. Where can I find data to back these numbers?

      [Anna]: About 21 days is the digit used very often, but this is related to very-very old and not proper research.  That is why I cite it, because people somehow heard about this.

      The recent well-known research is made by Lally P., Cornelia H. M., Jaarsveld v., Potts H. W. W. & Wardle J. (2010) How are habits formed: Modelling habit formation in the real world. European Journal of Social Psychology. October 2010. 40 (6), pg. 998-1009. They show the curve of timings of habit formation from 18 till 80+ days (depending on type of habit) and suggest that few days missing is not critical, so 15 is more accurate about minimal amount of execution of forming a habit.  If you consider, I can expand this explanation in the talk.

      You suggest to become hyper productive on needs to do the daily scrum at the same time, same place, in the same order of people and with the same set of questions in the same order. How practical do you think this is?

      [Anna] I find it practical enough so the ritual is formed. In my practice people tend to change it too much so they miss the opportunity to form the habit of day start using the powerful ritual.  This is all about opportunity to do better, nobody is punished for not following the recommendations if thisis not appropriate for them, but knowing what can be modified is benefitial.

       

       

       

  • Jerry Rajamoney
    By Jerry Rajamoney  ~  4 years ago
    reply Reply

    Hi Anna,

    Good Day. A very different topic. Thanks for choosing this topic. Out of curiosity I have the following question. I would like to know how are you going to map the fundamentals between "NeuroScience" & Scrum. You have beautifully explained the mapping between scrum rituals & NeuroScience. But Scrum is an Empirical process and
    NeuroScience is a very differnt one. In my experience I found the NeuroScience is very much used by Coaches (Life Coaches or Coaches like David Rock) & the whole domain of this is very different from Scrum.

    If you are not clear about my query please let me know.

    Thanks for your time.

    Regards,

    Jerry

    • Anna Obukhova
      By Anna Obukhova  ~  4 years ago
      reply Reply

      Hello Jerry,

      Thank you, the question is very interesting and clear.

      In my presentation I really map the neuroscience tips with the widely used Scrum rituals. The key there is to show that even standard Scrum framework has the full potential to boost your brain and results. You just need to know and use rather simple tips.

      I agree that Coaches use a lot of persuasion techniques that involve neuroscience knowledge (and I use them a lot, and even have a presentation about the techniques that Scrum Master and Coach can use to get the results). Thisis just not in the scope of this speech. If you feel that  it may be also interesting to speak about the SM/Coach approach to persuasion and using neuroscience tips in their work, please let me know, there is some time for the application left.

       

      Thanks,

      Anna Obukhova

      Agile Coach, Luxoft


  • Martin Fowler
    Martin Fowler
    Chief Scientist
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    In the last decade or so we've seen a number of new ideas added to the mix to help us effectively design our software. Patterns help us capture the solutions and rationale for using them. Refactoring allows us to alter the design of a system after the code is written. Agile methods, in particular Extreme Programming, give us a highly iterative and evolutionary approach which is particularly well suited to changing requirements and environments. Martin Fowler has been a leading voice in these techniques and will give a suite of short talks featuring various aspects about his recent thinking about how these and other developments affect our software development.

  • Liked Rae Abileah
    keyboard_arrow_down

    Rae Abileah - Engendering Justice: Women, War and Peace

    45 mins
    Keynote
    Beginner

    One in three women will be raped or beaten in her lifetime. Half of the seven billion global population are women so that means one billion women alive now will, or have been, beaten or raped or beaten. Women and children are disproportionately affected by war and occupation as well. And yet numerous studies illustrate how uplifting women's work and leadership can strengthen the whole society and economy. Women are at the forefront of global campaigns challenging militarism and violence, and working to redirect resources into health care, education, green jobs and other life-affirming activities. What can we learn from these women and their successes thus far? How can the technology sector support this crucial work? How do these social movements stay agile to rapidly respond to breaking news while building a long-term progressive movements for deeper social, economic and environmental justice? As Arundhati Roy said, "Another world is not only possible, she is on her way. On a quiet day, I can hear her breathing." In this talk, Rae Abileah will share visionary examples of women-led work for peace and justice and explore the paradigm shift needed for equality, human rights, and justice for all.

  • Liked Todd Little
    keyboard_arrow_down

    Todd Little - Leveraging Global Talent for Effective Agility

    Todd Little
    Todd Little
    Executive Consultant
    Accelinnova
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    A major challenge in agile development is the ability of test teams to keep pace with ongoing development while simultaneously ensuring that new development has not created regression failures. This case study from Halliburton shows how together with two globally distributed outsourcing partners they developed a comprehensive test automation strategy for their agile teams that effectively leveraged both in house and outsourced activities. This approach resulted in a significant quality improvement from prior releases.

  • Liked Ash Maurya
    keyboard_arrow_down

    Ash Maurya - How To Build Features People Will Want

    Ash Maurya
    Ash Maurya
    Founder
    Spark59
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    Most products fail. Not because we fail to build what we set out to build, but because we waste time, money, and effort building the wrong product.

    In this talk, I'll share our lean product development process that utilizes continuous customer feedback loops to ensure you don't go astray and instead build products people (will) want.

    What you'll learn:

    - How to track your your feature lifecycle on a validated learning kanban board
    - How to use qualitative testing techniques for early validation during the design and test phases
    - And then follow up with cohort based quantitative metrics to verify you have built something people wanted.

  • Liked Ryan Martens
    keyboard_arrow_down

    Ryan Martens - Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    CTO
    Rally Software
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Beginner

    Agile is not just a process change, its a mindset change for most. With faster time to market, better feedback and highly functioning teams, the Agile mindset opens our eyes to a better way of working as humans on large complicated and complex problems. Combining it with the concepts of Lean Startup, delivers another leap in team capacity and capabilities. It also opens the possibilities of using agility for more than just software development.

    Do you wonder how can we drive innovation in a disciplined way to tame our world's toughest problems? Can we apply the lessons learned from Agile and Lean Startup? Over the past three years, we've been able to apply agility at a new level, beyond business impact. Through our corporate social responsibility effort, "Rally for Impact", we aim to apply the agile mindset to mobilize citizen engineers to serve our communities and protect the planet. I want you to consider this growth path for yourself and your agile teams.

    Let's open the worlds mindset to a better way to empathize, explore and execute in these complex times.

  • Liked Jim McCarthy
    keyboard_arrow_down

    Jim McCarthy - Culture Hacking: The Prospect of Magnificence

    Jim McCarthy
    Jim McCarthy
    Founder
    McCarthy Technologies
    schedule 4 years ago
    Sold Out!
    60 mins
    Keynote
    Beginner

    A culture is the set of shared attitudes, values, goals, and practices that both describes and shapes a group. The unique challenges of creating software have demanded totally new types of corporate culture. In response, we have created Agile, Scrum, and XP and many other cultural disciplines. These represent the birth of culture engineering and, although significant, are primitive compared to what will follow. Jim McCarthy introduces "culture hacking," a kind of cultural engineering that focuses on protecting personal freedom, extending openness, and embodying rationality. In the near future, a system made up of shared commitments and interpersonal protocols for hosting cultural innovations is likely to become available and standardized, leading to enormous personal and collective cultural and productivity gains. Happily, these gains will be based on culturally designed nobility of purpose, and a potent and virtuous cycle will continue to emerge, whereby profit derives from ennobled behavior. This cycle will lead to an era of widespread and abundant greatness - an era of unparalleled magnificence.

  • Liked Dave Thomas
    keyboard_arrow_down

    Dave Thomas - Unknown Knowns

    60 mins
    Keynote
    Advanced

    In 2002, Secretary of Defense Donald Rumsfeld introduced us to the concepts of known knowns, known unknowns, and unknown unknowns. But he left out Unknown Knowns, things that we know without knowing it. And it turns out that these Unknown Knowns are actually the biggest category of knowledge - tacit knowledge.


    As developers, we work with knowledge: knowledge of the problem domain, knowledge of our tools, knowledge of our techniques, and knowledge of each other. So getting good at accumulating tacit knowledge is important.

    This talk will look at how we are poorly served by most of the current ways we are taught to be better developers. Can we do better? Only if we stop talking and start showing. Let's see why.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Advanced

    As the popularity of Agile methods have grown, so have the misconceptions or myths associated with Agile also grown. These myths get even more glorified when we talk about them in the offshore or distributed context. And to make matters worse, you can throw in a fixed-price contract spanner into the engine.

    Worry not! In this fun-filled activity, we'll collect facts from the participants that they believe are true and then we'll declare them as confirmed or busted after an interactive (heated) discussion.

  • Corey Haines
    Corey Haines
    CTO
    Wavetable
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    Everyone has acronyms, mnemonics, and a list of rules to guide their everyday software design. In order to get the most out of these age-old gems, one needs to deliberately practices them. Rules are a good way to remind ourselves of these gems.

    Corey Haines emphasies his design guidelines in form of the "4 Rules of Simple Design." Attend this talk to understand the four rules and their importance in everyday programming.

  • Liked Corey Haines
    keyboard_arrow_down

    Corey Haines - Stories from 10 Years of Extreme Programming

    Corey Haines
    Corey Haines
    CTO
    Wavetable
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    10 years ago I was introduced to Extreme Programming. Since then, I've been an avid practitioner, applying the techniques and values to my life as a software developer. Over that time, I've bounced between many extremes, learning and reflecting on the value that I get when building systems both for myself and for others.

    In this talk, I'll share some of those learnings and how my life as a software developer has changed with the times.

  • Liked Bernd Schiffer
    keyboard_arrow_down

    Bernd Schiffer - Net Promoter System for Agile Companies

    45 mins
    Talk
    Intermediate

    Customer collaboration is essential to every Agile business. To create and collaborate to keep a customer is the purpose of an organisation. But still lots of companies try to make bad profits, i.e. profits earned at the expense of customer relationships. The Net Promoter System (NPS) is a renowned open-source system which addresses and measures customer collaboration. And did you know that you not only can use it to get feedback on your products and services, but also on your employees and your personal performance?

    NPS is a perfect fit for Agile companies - and those who want to be. Most of the companies I worked with (Agile coaching, training, consulting) had not heard about it, and far less were actually using it. This really surprises me, since NPS integrates like a charm with Agile, e.g. within product development via Scrum.

    In this session I'll explain the basics of NPS, i.e. promoters and detractors, satisfied and delighted customers, bad profits (how to deal with bad feedback?) and good profits, and why and how to measure these. Several stories from companies like Apple Retail, Zappos, Southwest Airlines, and others will help to make my point. I’ll further show why NPS is a very good fit with Agile regarding products, employees, and personal performance. Dos and Don’ts regarding NPS (also from personal experience) will close this session. Related to the Don'ts, I also cover some of the negative critiques out there.

  • Liked Mukesh Bhangria
    keyboard_arrow_down

    Mukesh Bhangria - Continuous Refactoring at Amazon: A Case Study

    45 mins
    Talk
    Beginner

    Between the project deadlines, we always feel there is code which needs to be improved

    Usually Developers have the following 3 options:

    - Bite the bullet and do the refactoring as they go along.
    - Park the issue and address it later.
    - Allocate special time when the project gets out-of-control.

    As customer facing stories take higher priority, usually Developers are forced to choose the last option.

    However a team at Amazon took a different approach. Attend this session to listen to their first-hand story of how they changed this typical behavior to achieve Continuous Deployment on a critical service.

  • Liked Victoria Schiffer
    keyboard_arrow_down

    Victoria Schiffer - Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    Agile Coach
    SEEK
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    I love being around awesome people, who build great products customers desire. 
    I love learning from and together with these amazing minds. 
    I love creating the right environment for teams to flourish. 
    I love change, and learning from new experiences. 
    I love working in Agile environments.

    How about you? 
    I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.

    The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.

    In our everyday life doing Agile we already respect these aspects in many ways. 
    But do we practice what we preach as best we can?

    I'd like to challenge your current way of thinking about people and processes. 
    I'd like to challenge you to focus on you, before you focus on others. 
    I'd like to challenge your current way of reflecting. 
    I'd like to inspire you to go different ways. 
    I'd like to inspire you to inspire others.

    In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
    "You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.

    And why not take it even further? Why not go "Beyond Agile"?!

    Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.

    Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.

    In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.

    Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!

  • Liked Giovanni Asproni
    keyboard_arrow_down

    Giovanni Asproni - Methodology Patterns: a Different Approach to Create a Methodology for Your Project

    Giovanni Asproni
    Giovanni Asproni
    Consultant
    Asprotunity Limited
    schedule 4 years ago
    Sold Out!
    90 mins
    Tutorial
    Advanced

    In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

    In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

    The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - Scaling XP Practices inside your organization using Train-the-Trainer Model

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 mins
    Workshop
    Advanced

    How do you effectively scale skill-based, quality training across your organization?

    Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

    The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.

  • Liked Daniel Zen
    keyboard_arrow_down

    Daniel Zen - Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    CEO
    Zen Digital
    schedule 4 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    Agile & Test Driven Development of frontend JavaScript User Interface code is often passed over using the excuse that the UI code is "declarative" (What you see is what you get) and therefore does not 'need' to be tested. Others, will dismiss testing frontend AJAX code as too difficult to maintain or unnecessary because it is only important in context with the server. We will show how these misconceptions are false. 

    We will cover several popular JavaScript tools and technologies that make Agile frontend web development easy. We will show how these front end technologies cannot only be functionally tested, but Unit Tested. If time is available will cover Continuous Integration, Dependency Injection, & Mock objects.  

    By including your front-end code in your automated testing process you can prevent the inclusion of bugs that are usually only caught with manual testing.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

    Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

    Our main question was: As mobile app developers, how should we architect/design our apps for CD?

    We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

    If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

  • 45 mins
    Experience Report
    Intermediate

    Agile processes are the new order of IT implementations. These talk will elaborate on our experience and learnings during agile process implementation at Walmart. 

    We will touchupon following 3 key areas and our learnings that helped us scale agile in large enterprises.

    • Process Visualization - Our learnings related to visualization of existing processes and practices and how it helped us identify signals from noise

    • Product Backlog Elaboration - In a complex and large programs product backlog management and role of product owner needs to be revisited.

    • Team Working Agreement - This is particulary crucial for scaling agile as dependency management is one of the key aspects of enterpsie agile implementation.

    We will conclude with our key learning of how processes needs to be continuously evolved in large scale implementation.

  • Liked Pramod Sadalage
    keyboard_arrow_down

    Pramod Sadalage - Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    Developer
    ThoughtWorks
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

    1. 1. Encapsulate Table with View
    2. 2. Migrate method from database
    3. 3. Replace method with views
    4. 4. Introduce Read only table
    5. 5. Split table
    6. 6. Make column non-nullable
    7. 7. Drop column
    8. 8. Add foreign key constaint
    9. 9. Merge columns
    10. 10. Replace columns

    In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

  • Liked Cara Turner
    keyboard_arrow_down

    Cara Turner - Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    Agile Coach
    Khanyisa Real Systems
    schedule 4 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

    This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.