• Liked Pramod Sadalage
    keyboard_arrow_down

    Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    schedule 3 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 Johannes Brodwall
    keyboard_arrow_down

    Practice agile programming with coding dojo

    Johannes Brodwall
    Johannes Brodwall
    Buddhima w.wickramasinghe.
    Buddhima w.wickramasinghe.
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

    This is what previous participants say about the workshop:

    • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
    • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
    • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
  • Liked Ellen Grove
    keyboard_arrow_down

    Build Your Dreams: User Requirements Gathering with LEGO Serious Play

    Ellen Grove
    Ellen Grove
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

    This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

  • Liked Daniel Zen
    keyboard_arrow_down

    Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    schedule 3 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.

  • Liked Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 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.

  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

  • Ash Maurya
    Ash Maurya
    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 Mukesh Bhangria
    keyboard_arrow_down

    Continuous Refactoring at Amazon: A Case Study

    Mukesh Bhangria
    Mukesh Bhangria
    schedule 3 years ago
    Sold Out!
    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 Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

  • Liked Sreerupa Sen
    keyboard_arrow_down

    Changing our Rhythm: Our Ongoing Journey towards Continuous Delivery

    Sreerupa Sen
    Sreerupa Sen
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Annual software release cycles cramping the agility of the team? Too many hot fixes reducing the efficiency of your organization? Customers waiting impatientlyfor  the next cool features hot off the press? These are some of the painful and common problems faced by development teams worldwide. In today's world, most things get outdated or out-of-fashion very fast - and software is no different. Users cannot afford to wait for the next cool set of features for a year. They want a steady stream of cool new features that they can adopt and use immediately.

    My team follows a development model that we like to call Open Commercial Development - where we're always connected to our stakeholders, our plans are out in the open, and we're always gathering feedback and reprioritizing. We used to have yearly releases of our product - a sort of big bang release with a host of new featres. Based on our stakeholder interactions, however, we figured that our software delivery wasn't agile enough for our customers. Users wanted new features incrementally throughout the year. They especially didn't want to wait a year for a feature that they'd requested that was critical for their business.

    So began our journey to Continuous Delivery - an interesting one for sure. It's not easy to deliver new features, manage technical debt, collaborate with users and incorporate their feedback into the new features - once every quarter. To do it consistently, with quality and on time, you need to have a framework in place - a combination of planning, process, automation and team organization - that lets teams focus on the right things to get to DONE DONE for their new features, and at the same time manage their quality and tecnical debt. Over the past year, we like to think that we've put that framework in place, and that is what I'd like to talk about in this session.

  • Liked Ryan Martens
    keyboard_arrow_down

    Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    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 Tathagat Varma
    keyboard_arrow_down

    Designing agile feedbacks for agile learning - an experience report

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Feedback is perhaps the most important aspect of the overall agile lifecycle. If the feedback is too wide and shallow, it won't give enough actionable feedback. If it is too narrow and deep, it might fail to register feedback outside its focus area. So, how does one go about designing feedbacks that enable agile learning. We call them agile feedbacks.

    In this brief session, we will share an experience from designing agile feedbacks for agile trainings and workshops. The objective was to get most critical feedback in shortest amount of time to enable quick action planning. We created feedback that took a maximum of 5 minutes and enabled the most important learning in both, focussed as well as open-ended manner that allowed us to focus on the most critical items. We employed elements of Design Thinking and Rapid Iterative Testing and Evaluation (RITE) to improve the process and quality of feedback themselves. We will also be touching up these concepts and how effective they were.

  • Liked Richard Kasperowski
    keyboard_arrow_down

    Self-management and Self-organization: Agile Games with Motion

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Self-management and self-organization are important themes in Agile software development, but what do they actually look like?  We pontificate about worker empowerment, but then we revert to command-and-control: our product owners mandate project scope and deadlines, and our Scrum Masters assign tasks to team members.  Why can’t we let teams be self-organized and workers be self-managed?
     
    These activity-based learning activities are kinesthetic learning games.  Players learn by playing fun, physical games of movement.  These games create a social atmosphere and a full body and mind experience that make it easy and fun to learn.  We’ll play five games, including Line Up, 60 Paces, Triangles, Human Knot, and a special surprise game.
     
    In this session, we explore and experience self-management and self-organization via Agile games.  You will leave with a deep internalized understanding of self-management and self-organization and an appreciation of how they work better than command-and-control.  You’ll be able to share these games with your coworkers.

  • Liked Howard Deiner
    keyboard_arrow_down

    Pivoting Your Organization to Become Agile Testers

    Howard Deiner
    Howard Deiner
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Many organizations struggle with transforming from the old style teams consisting of members with specialized silos of skills into Agile teams consisting of generalized specialists.  This results in sub-optimal Agile adoptions in Agile/Scrum environments, which is where most organizations transforming to Agile are advised to start.

    We will start with a look into the real role of QA in the organization, and where they truly add value in the production of quality code to allow the business to move forward. Piggybacking on the role of QA, we will then speak to exactly what QA needs to do to add value to the software development process, and how they integrate in the DevOps model that is a contemporary solution to an age old issue.  And, finally, we will speak to some uncomfortable truths, and draw conclusions into the skills that Agile Testers must be expected to master to allow the organization to pivot successfully into a truly Agile development group.

  • Liked Nitin Ramrakhyani
    keyboard_arrow_down

    Lean Roots to Grow, Wings to fly!

    Nitin Ramrakhyani
    Nitin Ramrakhyani
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A lot has been said about Kanban and how these can be implemented in Software development, but the learning remains superficial till we go deep down to its roots to understand the core underlying practices and principles and why/how these practices evolved over a period of time. Infact the roots of most of the Agile methods can be traced back to Lean/Toyota Production Systems, a set of practices and techniques used by Toyota to build great set of cars with limited amount of resources. Even though building software is much different than building a car, there are many lessons and practices that can be learnt and applied nonetheless.

    In this interactive and visual talk, we'll take a virtual trip to Japan and learn some of the best practices/concepts that originated at Toyota for building "world-class" cars and see how each of these can be applied to software development. Learning about the roots of Lean should help the attendees in sowing the seeds of Lean improvement in their organizations and would help in building better software and improving the efficiency of the software delivery lifecycle.

  • 45 mins
    Workshop
    Beginner

    There is a level of "assumptions" that each one of us work with, while we deal with any system. Here in this case the system could be a team member, the manager, the management, or the entire organization. While we work with assumptions, the conversations or the discussions or the work we do, can seem like getting nowhere because of the conflicts, and a sense of frustration piles on .This is a common situation and a very common feeling amongst Coaches/Scrum masters/Project Managers or anyone dealing with project management scenarios. That is where "contracting" helps us get our way through!

    Contracting is a concept of "Transactional Analysis" school of psychology. Eric Berne defines it as "an explicit bilateral commitment to a well-defined course of action". Sometimes contracts will be multi-handed - all parties to the contract will have their own expectations. In the unusual event that these are all congruent, then fine. However, if not, then discussing everyone's expectations will lead to greater understanding and therefore to a clear contract. The risk in not doing this is that problems in completing the contract will emerge at some stage.

    3 Categories of contracts are administrative, professional and psychological.

    Administrative contracts deals with the operational agreements- like fees, who has to do what, time, frequency, attendees etc.

    Professional contracts deals with the expectations from each role and clarifies the essential setup required to achieve the same

    Psychological contracts talks about how we work as people and help to understand how we express our comforts/ discomforts       

    Amongst the three contracts psychological contracts are very essential and often ignored in projects. This type of contract will help us co-create any assignment and it’s a powerful tool for Agile coaches while they work with their teams, managers, organization etc.

    Further to agree with any contract, both the parties should operate from a space where there is mutual trust and concern (I am Ok , You are Ok).

    This report will discuss in detail about these contracts with examples from Agile projects, in an activity based sessions. We will also discuss the life positions based on 'I am OK, You are OK' theory.

    Note: Please note that this presentation is not about the business/financial contracts that most of us are aware of. However, the framework of contracts could be applied in any situation including the business/financial contracts.

  • Liked Shashank Teotia
    keyboard_arrow_down

    Polyglot Programming and Agile Development

    Shashank Teotia
    Shashank Teotia
    Pramod Sadalage
    Pramod Sadalage
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Advanced

    Polyglot Programming as a technique is not new and as a paradigm was coined in 2006 by Neal Ford. In today's world, we often architect solutions which need to be highly scalable, secure, efficient, have an engaging GUI, be extensible with low technical debt in parts or whole. To work with a single tech stack promotes a sense of mono culture which is detrimental and limiting the way a solution can be designed. Moreover, with multi-core machines available, processing now can leverage parallel processing and it maybe make more sense to use a language which takes away the overhead of the intricacies of multi-thread programming.

    In other words, in many cases, engaging in Polyglot Programming helps you focus more on the domain and adds to developer productivity.

    On the flip side, increasing the moving parts also means that if not designed well, Polyglot Programming could be a double edged sword and produce more mess in the way different pieces interact with each other.

    In this talk, we will showcase an ecosystem we built, involving a desktop device configuration backed, an OS-agnostic desktop GUI, a cloud service, a cloud cluster configuration tool and how we used the Agile principles, namely TDD, Continuous Integration and the works to be able to keep the polyglot ecosystem sane.

    Name wise, the languages/tools/etc which we used in our Polyglot case – Google Go, Node-Webkit, JS (Knockout/RequireJS), Ruby, Cucumber, RIAK, Chef, Lisp, Jenkins

     

  • Liked Mushtaq Ahmed
    keyboard_arrow_down

    Using a modern web framework for big enterprise agile project

    Mushtaq Ahmed
    Mushtaq Ahmed
    schedule 3 years ago
    Sold Out!
    20 mins
    Demonstration
    Advanced

    At ThoughtWorks, a 50-people team is building a marketing website backend for one of the largest consumer electronics brands in the world. We are Play-Scala as our web framework which allows us to design the application in a very different but powerful ways. This experience based talk will talk about these differences, emphasizing on two of them: "Dealing with concurrency without threads" and "Dependency resolution with constructor injection".

    Dealing with concurrency without threads
    - The backend is end to end non-blocking with highly concurrent architecture
    - Each page consists of 20+ reusable snippets, so each page request translates into 20+ outbound web service calls to get data for the snippet data in parallel
    - Posting data involves download/upload of large images from/to remote services, also done in parallel
    - We will show you how Scala Futures, Play and ReactiveMongo functional programming paradigm allows us to do all this without blocking any thread or managing thread-pools by hand

    Dependency resolution with constructor injection
    - Dependency injection is considered essential for designing applications that are easy to test. Usaully, dependencies are specified as constructors parameters
    - Scala traits allow us to get rid of constructors by wrapping classes and their factories inside components that in turn can depend on other components, this enables a compile time mechanism for dependency resolution which is very flexible
    - We will show examples of this pattern, its effects testing without external DI frameworks

    We will briefly talk on how functional programming style in general helps with testing and software delivery on agile projects. Finally, we will also cover the pain-points these approaches bring out, and argue if it is worth to pay that cost.

     

     

  • Liked Arlo Belshee
    keyboard_arrow_down

    Agility: Step 1: Discipline; Step 2: Make Awesome

    Arlo Belshee
    Arlo Belshee
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    What comes after Agile? That depends on what you did for Agile. We will start by talking about the practices - and results - that only the top 2% of agile teams do. For most teams, this is what is beyond their Agile. Then we'll talk about patterns in the things that these top 2% are trying. Everything comes from the insane disciple Agile teams possess; let's look at how they capitalize on it.

  • Liked Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Estimating software projects has proven to be particularly challenging. Over-running schedules happens frequently in our industry. Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

  • Liked Jez Humble
    keyboard_arrow_down

    Why The Project Paradigm Kills Innovation, and What To Do Instead

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Projects were invented as a vehicle for managing civil engineering projects. But software has completely different characteristics from, say, a bridge. In this talk I'll explain why the use of projects causes significant dysfunction, and how to build innovative products and services at scale based on lean principles.

  • Ash Maurya
    Ash Maurya
    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 Mukesh Bhangria
    keyboard_arrow_down

    Continuous Refactoring at Amazon: A Case Study

    Mukesh Bhangria
    Mukesh Bhangria
    schedule 3 years ago
    Sold Out!
    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.

  • Joe Zachariah
    Joe Zachariah
    schedule 3 years ago
    Sold Out!
    20 mins
    Others
    Beginner

    Often times, as an organization matures into its Agile adoption space, many people begin to start looking at Agile as just another process, and forget that the one of the main tenets for Agile is 'People over Processes'. Ultimately we are all here to build exciting, quality assured, on time and within scope products and along the way also have some fun. But what if the team does not gel well together, to such an extent that it begins to affect the quality of the deliverables?

    That's the time when we need to look within our bucket of Agile best practices to understand which of those we can employ to even build a stronger team. Practices such as pair programming, continuous builds, retrospectives, etc. are all best practices which when employed at the right moment and at the right time, can help a team get together. 

    In this presentation, I am putting together a few songs from Bollywood movies, to describe in a fun way a team's transition through the four stages of team building - forming, storming, norming and performing. And how using some Agile best practices, the team could tide over the storming phase and move over to the performing phase. 

    This will be a 20 minute presentation, in which the first 5 minutes I will be talking, followed by about 15 minutes of a fun video which would be a mish mash of Bollywood songs highlighting all that my team went through in their Agile journey

  • Liked Naresh Jain
    keyboard_arrow_down

    SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Nitin Ramrakhyani
    keyboard_arrow_down

    Lean Roots to Grow, Wings to fly!

    Nitin Ramrakhyani
    Nitin Ramrakhyani
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A lot has been said about Kanban and how these can be implemented in Software development, but the learning remains superficial till we go deep down to its roots to understand the core underlying practices and principles and why/how these practices evolved over a period of time. Infact the roots of most of the Agile methods can be traced back to Lean/Toyota Production Systems, a set of practices and techniques used by Toyota to build great set of cars with limited amount of resources. Even though building software is much different than building a car, there are many lessons and practices that can be learnt and applied nonetheless.

    In this interactive and visual talk, we'll take a virtual trip to Japan and learn some of the best practices/concepts that originated at Toyota for building "world-class" cars and see how each of these can be applied to software development. Learning about the roots of Lean should help the attendees in sowing the seeds of Lean improvement in their organizations and would help in building better software and improving the efficiency of the software delivery lifecycle.

  • Liked Ryan Martens
    keyboard_arrow_down

    Beyond Agile Execution: Agility for Business and Impact

    Ryan Martens
    Ryan Martens
    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 Karthik Sirasanagandla
    keyboard_arrow_down

    When Agile becomes Fr-agile..learn your lessons the fun way!

    Karthik Sirasanagandla
    Karthik Sirasanagandla
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    So you have heard of "Code Smells". Did you hear of "Agile Smells"? Yes or No; then this session is for you (us).
     
    In this session, Karthik intends to talk about the very many things that go wrong in companies that attempt to be or become Agile.
    But fault-finding is the easiest thing. Can Karthik provide concrete solutions? Yepp, he intends to share the solutions as well for most if not all the problems.
    And in same breadth seeks to know what others has to offer from their experience.
     
    Piquing your interest? Are you wanting to get a taste of some of the Agile smells? Below are some of them:
    * Belated Stand-ups
    * Non-participative stand-ups
    * War-zone Retrospectives 
    * Unfruitful Sprint planning meeting
    * Zero-Test development
    * Inverted Test Pyramid development
    * Gate-keeper QAs
    * Hierarchical Roles
    * Velocity Driven Development
     
  • 45 mins
    Workshop
    Beginner

    There is a level of "assumptions" that each one of us work with, while we deal with any system. Here in this case the system could be a team member, the manager, the management, or the entire organization. While we work with assumptions, the conversations or the discussions or the work we do, can seem like getting nowhere because of the conflicts, and a sense of frustration piles on .This is a common situation and a very common feeling amongst Coaches/Scrum masters/Project Managers or anyone dealing with project management scenarios. That is where "contracting" helps us get our way through!

    Contracting is a concept of "Transactional Analysis" school of psychology. Eric Berne defines it as "an explicit bilateral commitment to a well-defined course of action". Sometimes contracts will be multi-handed - all parties to the contract will have their own expectations. In the unusual event that these are all congruent, then fine. However, if not, then discussing everyone's expectations will lead to greater understanding and therefore to a clear contract. The risk in not doing this is that problems in completing the contract will emerge at some stage.

    3 Categories of contracts are administrative, professional and psychological.

    Administrative contracts deals with the operational agreements- like fees, who has to do what, time, frequency, attendees etc.

    Professional contracts deals with the expectations from each role and clarifies the essential setup required to achieve the same

    Psychological contracts talks about how we work as people and help to understand how we express our comforts/ discomforts       

    Amongst the three contracts psychological contracts are very essential and often ignored in projects. This type of contract will help us co-create any assignment and it’s a powerful tool for Agile coaches while they work with their teams, managers, organization etc.

    Further to agree with any contract, both the parties should operate from a space where there is mutual trust and concern (I am Ok , You are Ok).

    This report will discuss in detail about these contracts with examples from Agile projects, in an activity based sessions. We will also discuss the life positions based on 'I am OK, You are OK' theory.

    Note: Please note that this presentation is not about the business/financial contracts that most of us are aware of. However, the framework of contracts could be applied in any situation including the business/financial contracts.

  • Liked Puneet Sachdev
    keyboard_arrow_down

    Biting the Bullet - CMMi Level 5 Assessment for Agile Programs

    Puneet Sachdev
    Puneet Sachdev
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    CMMi Level 5 assessment has been a necessity and a hygiene factor for any service organization. Our organization has been assessed at Level 5 continuously since 1999. However, with spread of Agile methodologies in offshore scenarios we were faced with a question of ensuring CMMi compliance in Agile programs.

    This session will delve into details of our CMMi journey for Agile programs and how NIIT Technologies successfully got re-assessed at CMMi Level 5 with Agile in August 2013. The session will talk about various mapping of agile practices with CMMi process areas, identified gaps and how these gaps were addressed to ensure a successful assessment without diluting the Agile promise. 

    Some examples of how various process areas have been mapped to various agile practices. The session will be mostly example based and experience sharing. 

    Example 1 (Level 2 Maturity)

    CMMi Requirements Management PA talks about bidirectional traceability. If you go to sub practice (SP 1.4 of Requirements Management PA) level then there are three requirements: 

    • 1) Maintain requirements traceability to ensure that the source of lower level (i.e., derived) requirements is documented.
    • 2) Maintain requirements traceability from a requirement to its derived requirements and allocation to work products.
    • 3) Generate a requirements traceability matrix.

    Looking at the above, we managed this through requirements management being done in Agile projects using tools like Rally, TFS (agile templates), Jira Greenhopper and NIIT's internal agile management tools. These tools provide traceability from Epics --> Stories --> Tasks --> Test Cases --> Defects. This fullfils the intent of the PA. Hence we do not explicitly generate any RTM especially for agile projects (3rd bullet above) as the intent is already met. 

    Example 2  (Level 2 Maturity)

    CMMi Project Monitoring and Control (PMC) PA talks about a goal "Manage Corrective Actions to Closure" (SG2). This has 3 separate sub processes

    • 1) Analyze Issues
    • 2) Take corrective Action 
    • 3) Manage Corrective Action

    All these have been covered through the Agile practice of having "retrospectives", which happen regularily in Scrum. Retrospectives is where the people point out issues amongst other things, discuss what actions can be taken to improve and/or address the problem at hand. These action items coming out of retrospectives are then tracked as they would normally  have been done to closure. We do not mandate any specific format/tool for capturing and tracking this information.  

    Example 3 (Level 4 Maturity)

    CMMi Organization Process Defintion PA, has a goal for "Establishing Performance Baselines and Models" and a Sub Practice "Analyze Process Performance and Establish Process Performance Baseline".

    Here instead of taking traditional  metrices like productivity (hrs/FP), schedule slippage etc. we have taken metrices which are more close to the agile process. Examples of these are: 

    • 1) UAT Defects per Engineering Effort Unit
    • 2) Velocity Improvement over time
    • 3) % of story point change to measure requirements stability   
  • Liked Sreerupa Sen
    keyboard_arrow_down

    Changing our Rhythm: Our Ongoing Journey towards Continuous Delivery

    Sreerupa Sen
    Sreerupa Sen
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Annual software release cycles cramping the agility of the team? Too many hot fixes reducing the efficiency of your organization? Customers waiting impatientlyfor  the next cool features hot off the press? These are some of the painful and common problems faced by development teams worldwide. In today's world, most things get outdated or out-of-fashion very fast - and software is no different. Users cannot afford to wait for the next cool set of features for a year. They want a steady stream of cool new features that they can adopt and use immediately.

    My team follows a development model that we like to call Open Commercial Development - where we're always connected to our stakeholders, our plans are out in the open, and we're always gathering feedback and reprioritizing. We used to have yearly releases of our product - a sort of big bang release with a host of new featres. Based on our stakeholder interactions, however, we figured that our software delivery wasn't agile enough for our customers. Users wanted new features incrementally throughout the year. They especially didn't want to wait a year for a feature that they'd requested that was critical for their business.

    So began our journey to Continuous Delivery - an interesting one for sure. It's not easy to deliver new features, manage technical debt, collaborate with users and incorporate their feedback into the new features - once every quarter. To do it consistently, with quality and on time, you need to have a framework in place - a combination of planning, process, automation and team organization - that lets teams focus on the right things to get to DONE DONE for their new features, and at the same time manage their quality and tecnical debt. Over the past year, we like to think that we've put that framework in place, and that is what I'd like to talk about in this session.

  • Liked Arlo Belshee
    keyboard_arrow_down

    Agility: Step 1: Discipline; Step 2: Make Awesome

    Arlo Belshee
    Arlo Belshee
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    What comes after Agile? That depends on what you did for Agile. We will start by talking about the practices - and results - that only the top 2% of agile teams do. For most teams, this is what is beyond their Agile. Then we'll talk about patterns in the things that these top 2% are trying. Everything comes from the insane disciple Agile teams possess; let's look at how they capitalize on it.

  • Liked Bhuwan Lodha
    keyboard_arrow_down

    Building a Team Backlog: The Power of Retrospectives

    Bhuwan Lodha
    Bhuwan Lodha
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

  • Liked Mushtaq Ahmed
    keyboard_arrow_down

    Using a modern web framework for big enterprise agile project

    Mushtaq Ahmed
    Mushtaq Ahmed
    schedule 3 years ago
    Sold Out!
    20 mins
    Demonstration
    Advanced

    At ThoughtWorks, a 50-people team is building a marketing website backend for one of the largest consumer electronics brands in the world. We are Play-Scala as our web framework which allows us to design the application in a very different but powerful ways. This experience based talk will talk about these differences, emphasizing on two of them: "Dealing with concurrency without threads" and "Dependency resolution with constructor injection".

    Dealing with concurrency without threads
    - The backend is end to end non-blocking with highly concurrent architecture
    - Each page consists of 20+ reusable snippets, so each page request translates into 20+ outbound web service calls to get data for the snippet data in parallel
    - Posting data involves download/upload of large images from/to remote services, also done in parallel
    - We will show you how Scala Futures, Play and ReactiveMongo functional programming paradigm allows us to do all this without blocking any thread or managing thread-pools by hand

    Dependency resolution with constructor injection
    - Dependency injection is considered essential for designing applications that are easy to test. Usaully, dependencies are specified as constructors parameters
    - Scala traits allow us to get rid of constructors by wrapping classes and their factories inside components that in turn can depend on other components, this enables a compile time mechanism for dependency resolution which is very flexible
    - We will show examples of this pattern, its effects testing without external DI frameworks

    We will briefly talk on how functional programming style in general helps with testing and software delivery on agile projects. Finally, we will also cover the pain-points these approaches bring out, and argue if it is worth to pay that cost.

     

     

  • Niranjan N V
    Niranjan N V
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Usage of Agile methodologies such as Scrum, Scrum-XP, FDD, Crystal and methodologies has become increasingly large in IT Industry and also non IT industries. As the usage of agile methods becoming wide spread, the effectiveness of implementation of these agile practices in projects, organizations become more important for success of agile. Agile manifesto and 12 agile principles, acts as guiding principles and helps in the agile deployment. But when it comes to operational daily tasks, there is no method to ensure whether agile projects implement 4 values of manifesto. For traditional methods of software development we have standards such as CMMI,ISO etc. This paper makes an attempt to defining Maturity Model for agile projects.

    Following maturity model has been defined after our experience in consulting and training agile methods.

    Level

    Categorized by

    Guidelines for Description

    Maturity Rating based on Focus Areas

    1

    Basic

    1) Following traditional Water fall approach for delivery. 2) Agile practices used in pockets. 3) Requirements/Features (Product backlog items) are more at high-level or Epics levels

    Any Focus area <= 50%. Overall Compliance <=50%

    2

    Managed

    1) Product backlog items are broken from EPICs   into development user stories, product back log grooming is done 2) Basic metrics used and not very strong in prediction of the current performance, timeliness of deliverables 3) The Agile team delivers business value occasionally

    All Focus Areas - 50% and 75%. Over-all compliance- 50-75%

    3

    Matured

    1) Iteration Status , Agile Metrics in place using Agile Tasks Board 2) Usage of historic data such as velocity, story points committed v/s delivered for forecasting and estimation 3) Team reports the Iteration Effectiveness, Release Effectiveness to different levels of management like functional manager, Product Owner and Top management. 4) Team is skillfully using the Agile Engineering Practices in projects if not at Program Levels

    All Focus Areas - >75% Overall compliance > 75%

    To validate the maturity levels defined, an assessment of agile practices in projects are done and mapped into following focus areas.

     

    Focus Areas

    Development Practices/ Infrastructure

    Iteration Planning/ Tracking

    Product Ownership

    Release Planning/ Tracking

    Team Cohesiveness( Collaboration)

    Agile Testing Practices

     

    In order to rate the maturity levels for any project, the compliance of agile practices are mapped into above focus areas and Radar Chart is plotted to depict the compliance of each of these focus areas and are the agile mturity in projects.

     

     

     

     

  • Liked Prabhakar Karve
    keyboard_arrow_down

    Inspect and Adapt – Powerful technique to increase productivity through continuous improvement

    Prabhakar Karve
    Prabhakar Karve
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    Inspect & adapt is an important agile practice. Inspection helps us to see the reality beyond our filters. Better awareness of reality helps us to more effectively re-plan our work and modify our existing way-of-working.

    There are multiple benefits of this practice, but in this workshop we focus on how it can lead to continuous improvement in productivity.

    Inspect and adapt can be used while carrying out regular work activities across the entire agile life cycle. However our focus will be on the Scrum ceremonies and common artifacts.

    In this workshop, through discussions and exercises, we explore Innovative ways to expand our capability to carry out inspection & adaptation, without adding any extra overhead.

    During the session you also get a few simple yet powerful tips which can be practiced immediately once back from the conference.

  • Liked Zaheerabbas Contractor
    keyboard_arrow_down

    Applying Agile Practices in the Refurbishment/Modernization of my housing society

    Zaheerabbas Contractor
    Zaheerabbas Contractor
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the rush to be a proud owner of a large independent penthouse apartment in a huge housing society I did not realize (or did not want to) the actual reason behind this good bargain!

    I ended up being party to the following list (product backlog) of pain areas (or business needs) of the society members:

    • 1.Need of Generator backup to cater to the frequent power cuts at least for the common areas and lifts (I had bought my condominium on the top floor and could realize the pain!) – Must have and High Cost
    • 2.Modernization of the ageing lifts across 18 buildings (thanks to the substandard quality lifts which I realized when I started staying there L ) – Must have due to high risk however huge Cost
    • 3.Need for the CCTV Camera – Must have considering the frequent untoward incidents
    • 4.Seepage and septic tank upgrade
    • 5.Pavements, speed breakers
    • 6. And the list goes on….

    This resulted into the society being least valued in that area and no ROI for the members who had invested in the society.

    The society committee members were clueless on where to start (prioritizing with business value) with the given evolving budget and how to manage the timeline.

     Through this report, I intend to share how I utilized following Agile practices to overcome the challenges faced by the society members for its refurbishment and converted the society into one of the most sought out society over the period of few milestones (releases)!

    • 1.Prioritization(MoSCoW) of the backlog by agreeing up urgent need of the society in the given budget
    • 2.Continuous planning and re-prioritization of product backlog
    • 3.Outcome(Value) based agreement with various vendors
    • 4.Managing discipline in the acceptance criteria and retrospection (i.e. PWD lift inspection and approval for lifts functioning with the given municipality specifications and taking learning to replicate the same for future enhancements)
    • 5.Delivering end to end(INVEST) in the production in short releases ( i.e. one lift modernization end to end and commissioning of Diesel Genset end to end through incremental approach)
  • Dipesh Pala
    Dipesh Pala
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    Breaking up User Stories can sometimes be as painful as a relationship break up - but it does not have to be like that!

    Our experience has shown us that the key to getting full benefit from introducing Agile is in how the project work is broken up. When it gets difficult to see how to write small enough user stories, teams often resort to technical story cards. While this can give the team visibility of the work that is being done, the business is not seeing potentially implementable product, or early delivery of business value.

    This talk will dig a lot deeper to expose the real reasons for splitting up user stories and not just talk about doing it as a good practice - we must BE Agile not just DO Agile!

    Using real-world examples, this talk will also offer a set of guidelines and some unconventional ways for breaking up larger chunks of work into valuable user stories that can help Agile teams become more successful.

  • Liked Vinay Krishna
    keyboard_arrow_down

    Effective 9 Practices to minimize technical debt

    Vinay Krishna
    Vinay Krishna
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt.
    While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many agile practitioners have suggested some practices to avoid or eliminate Technical Debt.
    In this session I shall discuss about a method to get relief from Technical Debt and talks about nine proven practices that a developer can follow to minimize Technical Debt. These practices help to:

    • Change the coder's mindset so that they should use technical practices i.e. various refactoring techniques to reduce technical debt in code and design
    • Developers to plan and manage the time to pay down the debt i.e. determine your living budget
    • Take minimal technical credit in design and code

    These practices have been used and found to be effective when implemented in projects which will be used as a case study.

  • Liked Daniel Zen
    keyboard_arrow_down

    Agile Engineering Javascript with Jasmine & AngularJS, Karma & Jenkins

    Daniel Zen
    Daniel Zen
    schedule 3 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.

  • Liked Jayaprakash P
    keyboard_arrow_down

    Agile doesn't improve quality. Can we release a world class product?

    Jayaprakash P
    Jayaprakash P
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    There is a common concern by management that Agile doesn’t make a difference to the product quality. How do we release a product of world class quality?

     Problem is two folded:

    1. 'Definition of Done' is not created with Quality in mind, nor is it measured against the quality set at the beginning of the project.
    2. Quality Goals and subsequent adherence ensures quality is met and not just meeting 'Definition of Done' (DOD) criteria. For example DOD may be met, but quality may still be poor if not managed appropriately. How – lets discuss this through the session.

     Once the quality goals are defined for a project, Definition of Done should align with these quality goals.

    At McAfee, we have released world class quality products through Agile Methodology and Quality Best Practices together. One exceptional method we practice is by defining and tracking "Effective Quality Goals" for each sprint, and at every release.

    By driving agile projects through quality goals, we have products with ZERO defects deferred / logged by customers, 90+% code covered through automated test, 70% defects found early through development practices. This magic was not in just one project, but close to a dozen projects in the last 3-4 quarters.

    In this presentation, we will explain about how we changed the paradigm in the last 2 years and released world class quality products in a short span of time.

  • Liked Pramod Sadalage
    keyboard_arrow_down

    Ten Patterns of Database Refactoring

    Pramod Sadalage
    Pramod Sadalage
    schedule 3 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 Gerry Kirk
    keyboard_arrow_down

    Create an Agile virus in your organization, empower your team, change your life

    Gerry Kirk
    Gerry Kirk
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Need buy in from a key manager or executive to adopt Agile? Desiring better team collaboration? Hungry for a saner life at home?
    Try Personal Kanbanwinner of the Shingo prize for Operational Excellence. It's the fastest, simplest way to taste test the goodness of the Lean Agile approach to managing knowledge work. Personal Kanban empowers small teams and individuals, at work and at home.Give that overwhelmed executive instant relief. Build your own system, and soon curious onlookers ask and then create their own. Look out, you've just released an Agile virus in your organization!
    You've also discovered a way for you and your team to get more out of your efforts, to improve communication, and find time for the things that matter most.In this session you'll learn how to create a Personal Kanban system through stories, examples and interactive exercises. Walk away understanding the psychology behind visualizing work and limiting work in progress, inspired and motivated to make a difference at work and home. 

  • Liked Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 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.

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Practice agile programming with coding dojo

    Johannes Brodwall
    Johannes Brodwall
    Buddhima w.wickramasinghe.
    Buddhima w.wickramasinghe.
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    A Coding Dojo is a fun and social way to become a better programmer. Johannes is an experienced coding coach who will guide you through a few hours of programming that will transform your understand your craft and yourself as a programmer. In the workshop you get to try out pair programming, test-driven development and continuous refactoring for yourself and you get lots of recommendations on how to improve your coding and testing. You will need to bring your own computer with a development environment of your choice. Recommended for Java, Ruby, JavaScript and C# developers.

    This is what previous participants say about the workshop:

    • What did you learn? New tools, pair programming and fun exercises; Ide tricks, programming language basics, testing tools, using tests as a reasoning tool; you can comfortably pair with strangers.
    • What surprised you? Small steps work better than planning; It's easy to get started when you pair program; Pair programming is nice
    • What do you plan to do next? Using TDD every day; Listen to partner more carefully - he may already have solved the problem.
  • Liked Michael Heydt
    keyboard_arrow_down

    Applying Lean UX to Capital Markets - Lessons From a Year of Lean UX on Wall Street

    Michael Heydt
    Michael Heydt
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Lean UX approach to interaction design is a spectacular model for defining and implemented what is needed in appications to support the users in their jobs, as compared to technical deliverables that in the end often do not meet the needs of the users.  In this talk, I will go over strategies for applying lean UX practices to capital markets projects, adapting UX to agile processes, including executing user interviews, rapid UX design, mockups to UI prototypes, and rapid implementation through continuous delivery and end user experience / acceptance testing.

  • Liked Priyank
    keyboard_arrow_down

    Deriving business case for a Product development ( using Agile Innovation Game )

    Priyank
    Priyank
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    In this session participants will learn how to 'derive a business case for a product' using simple method aka AGILE GAME (also known as Innovation Games, Gamestorming )

    Agile innovation games are one of the most effective way to solve a business problem or derive a solution. (For detail refer: www.innovationgames.com)  Participants will play Hot Air Balloon game to 'derive a business case for a product'. This game can help  -

    • Derive a Business Case
    • Identify Constraints & the path to solution.
    • Get multiple stakeholders on the same page
    • Identify RAIDS upfront
    • Plan to mitigate risk early in the cycle
  • Liked Ellen Grove
    keyboard_arrow_down

    Build Your Dreams: User Requirements Gathering with LEGO Serious Play

    Ellen Grove
    Ellen Grove
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

    This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

  • Liked Shashank Teotia
    keyboard_arrow_down

    Polyglot Programming and Agile Development

    Shashank Teotia
    Shashank Teotia
    Pramod Sadalage
    Pramod Sadalage
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Advanced

    Polyglot Programming as a technique is not new and as a paradigm was coined in 2006 by Neal Ford. In today's world, we often architect solutions which need to be highly scalable, secure, efficient, have an engaging GUI, be extensible with low technical debt in parts or whole. To work with a single tech stack promotes a sense of mono culture which is detrimental and limiting the way a solution can be designed. Moreover, with multi-core machines available, processing now can leverage parallel processing and it maybe make more sense to use a language which takes away the overhead of the intricacies of multi-thread programming.

    In other words, in many cases, engaging in Polyglot Programming helps you focus more on the domain and adds to developer productivity.

    On the flip side, increasing the moving parts also means that if not designed well, Polyglot Programming could be a double edged sword and produce more mess in the way different pieces interact with each other.

    In this talk, we will showcase an ecosystem we built, involving a desktop device configuration backed, an OS-agnostic desktop GUI, a cloud service, a cloud cluster configuration tool and how we used the Agile principles, namely TDD, Continuous Integration and the works to be able to keep the polyglot ecosystem sane.

    Name wise, the languages/tools/etc which we used in our Polyglot case – Google Go, Node-Webkit, JS (Knockout/RequireJS), Ruby, Cucumber, RIAK, Chef, Lisp, Jenkins

     

  • Liked Tathagat Varma
    keyboard_arrow_down

    Designing agile feedbacks for agile learning - an experience report

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Feedback is perhaps the most important aspect of the overall agile lifecycle. If the feedback is too wide and shallow, it won't give enough actionable feedback. If it is too narrow and deep, it might fail to register feedback outside its focus area. So, how does one go about designing feedbacks that enable agile learning. We call them agile feedbacks.

    In this brief session, we will share an experience from designing agile feedbacks for agile trainings and workshops. The objective was to get most critical feedback in shortest amount of time to enable quick action planning. We created feedback that took a maximum of 5 minutes and enabled the most important learning in both, focussed as well as open-ended manner that allowed us to focus on the most critical items. We employed elements of Design Thinking and Rapid Iterative Testing and Evaluation (RITE) to improve the process and quality of feedback themselves. We will also be touching up these concepts and how effective they were.

  • Liked Richard Kasperowski
    keyboard_arrow_down

    Self-management and Self-organization: Agile Games with Motion

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Self-management and self-organization are important themes in Agile software development, but what do they actually look like?  We pontificate about worker empowerment, but then we revert to command-and-control: our product owners mandate project scope and deadlines, and our Scrum Masters assign tasks to team members.  Why can’t we let teams be self-organized and workers be self-managed?
     
    These activity-based learning activities are kinesthetic learning games.  Players learn by playing fun, physical games of movement.  These games create a social atmosphere and a full body and mind experience that make it easy and fun to learn.  We’ll play five games, including Line Up, 60 Paces, Triangles, Human Knot, and a special surprise game.
     
    In this session, we explore and experience self-management and self-organization via Agile games.  You will leave with a deep internalized understanding of self-management and self-organization and an appreciation of how they work better than command-and-control.  You’ll be able to share these games with your coworkers.

  • Michael O'Reilly
    Michael O'Reilly
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    Test Requirement Driven Development(TREDD) places a renewed emphasis on quality and accountability, and provides the insight to allow your product development and management teams to make the necessary changes in order to produce outstanding quality products on schedule, in a cost-efficient and highly collaborative manner.

    What separates TREDD from other development methodologies like TDD (test driven development), ATDD (acceptance test drive development), or BDD (behavior driven development), is the status of the test requirement when the product development lifecycle concludes.

    Test Requirement status is the breakthrough element that allows test requirement to provide an objective measurement to the quality of the product development team, so that adjustments can be made for subsequent product development iterations that will ensure quality improves, as well as increase the effectiveness of the product development team.

    Come and learn how your TREDD will catalyze your SCRUM team toward greater capabilities, quality, accountability, and satisfaction!

  • Mark Collins-Cope
    Mark Collins-Cope
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Intermediate

    This talk discusses a reference architecture for object-oriented/component based systems consisting of five strata (or layers**).

    The purpose of the talk is to show how this large-scale application model helps us to understand the overall structure of a system, how strata help us to clarify our thoughts, and how it encourages the separation of concerns such as the technical v. the problem domain, policy v. mechanism, and the buy-or-build decision - and of course why this style of architecture is relevant to ease of refactoring and software restructuring under changing and multiple requirement sets.

     

    Assuming an application is made up of a number of components, the strata proposed is based on how specific to the particular requirements of an application each component is. More specific (and therefore less reusable) components are placed in the higher layers, and the more general, reusable components are in the lower layers. Since general non-application components are less likely to change than application specific ones, this leads to a stable system as all dependencies are downward in the direction of stability, and so changes tend not to propagate across the system as a whole.

     

    ** regarding: layers
    As well as presenting the reference model, this talk also discusses and clarifies in concrete terms the meaning of one architectural layer being above another. Perhaps surprisingly, the meaning of the layering metaphor is the subject of some confusion. Specific examples of this are given in the talk - though not yet shown on the slides.

    (Note; this is suggested a 90 minute presentation however it can be extended to a full half-day, one day or two day workshop. I also have two other agile presentations which I can submit if interest is there - these cover agile planning).

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    Why not estimate? Think different for story point estimation.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The Agile Community talks a lot about Estimation and need for it. A large majority have different opinions, but when it comes to teams and organizations that are transforming to Scrum, mostly suffer in group estimation and story point estimation technique. 

    Agile primarily focus on value based deliver and that doesn't need estimation. 

    This presentation enrich those audience who need estimations for their project/product development, with details that make estimates better. At the same time it doesn't advocate estimation as a must have for product development.

    Following 4 aspects will be connected to story point estimation and help audience understand the story-point estimation.

    1. Concept of Accuracy and Precession

    2. Cone of Uncertainty

    3. Story point Estimation scale

    4. Group Estimation and Relative Estimation

    Teams struggle in estimating the product backlog items. Composition of estimation: any estimate is a mix of "the known, unknown and complexity". The presentation shall also connect estimation thoughts to product backlog and the cone of uncertainty

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    4 Quadrant: Focus Area based Team Retrospective.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    The Regular and most popular retrospectives end with action items on the specific person in the team. 

    while the retrospective's primary goal is to enable the team to reflect onto themself and tune their behaviour for becoming more effective. In order to provide such a platform I practiced and coached 4 quadrant, focus area based retrospectives.

    In which the team focus on the over all improvement and not just an action item. this is truely the team's behavioural change and their actions to become more effective. 

    Based on many successful coaching experience, i would like to present this activity based session.

    Summary:

    The team identify the focus areas for improvements, then identifies the small delta improvement in that focus area that is measurable. then they decide on if they need external coaching or internally the team can achieve the goal.

     

    Focus areas | Coaching/Training

    _________________________

    Measurement | Self / team 

  • Liked Johannes Brodwall
    keyboard_arrow_down

    Bare-Knuckle Web Development

    Johannes Brodwall
    Johannes Brodwall
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Can you go faster with less weight?

    We have all learned the benefit of reusing application servers like JBoss, ORMs like NHibernate or dependency injection frameworks like Spring that "solve all the plumbing code for you", but how real are these benefits really? Most developers struggle using techniques like test-driven development and refactoring effectively in their day to day project. Many developers spend a majority of their day finding out which magic incantations will make your framework solve your requirement.

    Yes, frameworks probably will reduce the size of your code base. But will their reduce the time it takes to develop that code base? And perhaps even more pressingly: How certain are your estimates when you know that a the majority of your work is to find out exactly which few lines of code you need to change by debugging, reading documentation and searching for answers on stack overflow?

    When I was first learning math, my dad told me that I didn't to use a calculator before I could do the math without it. In the same tradition, this talk builds on the premise that you shouldn't use a framework that you can't do without: I will create, live, a realistic web application without generators, without frameworks and without bullshit. Instead, I will use test-driven development to ensure steady progress to a solution with no magic.

  • Liked Sreekanth Tadipatri
    keyboard_arrow_down

    Help teams succeed, so that your business succeeds

    Sreekanth Tadipatri
    Sreekanth Tadipatri
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    This presentation discussess some of the factors that are critical to the success of the teams.  Successful teams is a prerequisite to a successful enterprise.

    What would help the team succeed?

    What would hinder the teams?

    What are some things that might work for the team, but might not work for an enterprise?

     

    The above is an example of what will be discussed during the session.

  • Liked Yashasree Barve
    keyboard_arrow_down

    Why can’t Enterprise have all the Fun? –Tales from Enterprisy DevOps Land

    Yashasree Barve
    Yashasree Barve
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the age of continuous deployments, where Googles and Facebooks of the world push newer features every now and then, without any down time to millions of users! Enterprises and Users of internal IT systems within Enterprise are still stuck with old time consuming processes that take ages to churn out new features to business. Why can’t Enterprises have this fun!


    This is a story of an Enterprise that adopted and got mature in its Agile Adoption. The sponsors could see value every sprint, but it took time to translate this value to end users. Drive to sustain agility as well as getting things out to end users quickly needed to take a great momentum.


    Experimenting with DevOps came as a natural extension to this Agile-Scrum adoption. We would like to talk about the how the idea of DevOps implementation in this Enterprise originated, the various challenges met at the initial stages, carving the road map and our journey. We would highlight the benefits that we reap out of this effort as well as share best practices from what we have learnt.

  • Liked Ganesh Samarthyam
    keyboard_arrow_down

    Refactoring for Design Smells - With Examples from OpenJDK

    Ganesh Samarthyam
    Ganesh Samarthyam
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    Refactoring has received considerable attention in the last decade given the important role it plays in Agile methods. With Martin Fowler popularizing ‘code smells’ in his classic book on Refactoring, most programmers know about smells. However, refactoring design smells and architecture smells is also equally important for creating high quality software. This presentation introduces important design smells and the refactoring strategies for addressing them. The talk includes interesting examples of design smells found in OpenJDK 7.0 (Open source Java Development Kit) code base.