This is a hands-on programming session in which the winning teams will receive fabulous prizes (masquerading as cheap candy). The point of the session has to do with the basis for awarding candy to the winning teams. We do not wish to reveal that point in advance.

 

 

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

Outline/structure of the Session

Working in teams of two, you will complete a time-boxed programming challenge using the language and development environment of your choice. Bring a laptop that is configured to support your preferred development environment. Be prepared to let others use the laptop from time to time.

The point of the exercise is revealed in the details of the reward system by which you will earn your candy. Those details will be revealed midway through the session, after you have completed the first round.

Yes, that is correct: You will not know the basis for rewards until after you have completed the first round of the programming challenge.

We'll have a debrief and discussion at that point. Then you will engage in a second programming challenge. This time, you will know the secret of the reward system at the outset. (The "secret" will come as no surprise if you are accustomed to agile thinking.)

In a final debrief and discussion, we will explore the things you did differently in the second round and your reasons for doing them differently.

Learning Outcome

Food for thought regarding how we tend to approach software engineering work when we are part of a collaborative team, as opposed to when we are working on our own.

Target Audience

Anyone who works on or with agile software development teams, provided they have programming skills.

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Dave Nicolette
    keyboard_arrow_down

    Dave Nicolette - Using Lego to visualize Cycle Time and Process Cycle Efficiency

    Dave Nicolette
    Dave Nicolette
    Consultant
    Neo Pragma LLC
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    When delivery issues are made visible, there is often an immediate and natural change in behavior. In this session I will demonstrate a simple technique we have used with several teams at my current client to track Cycle Time and Process Cycle Efficiency (PCE) using Lego. In some cases, team members started to behave differently right away, as soon as they saw where the time was going. Two interesting effects occurred naturally, without any training. First, teams that saw a lot of red Lego on their boards adjusted their work in process (WIP). They didn't know the term "WIP" but they could see the effect and acted appropriately on the information. Second, the moment a team mate placed a red brick on the board, other team members asked what the impediment was and how they could help remove it. 

  • Liked Diane Zajac-Woodie
    keyboard_arrow_down

    Diane Zajac-Woodie - There’s No “I” in Team, But Should There Be?

    90 mins
    Panel
    Intermediate

    Scrum suggests that business analysts, testers and developers shed their old job titles and don the badge of “team member.” And current trends like mob programming further encourage team members to abandon their individual goals in the interest of team achievements. It seems there really is no “I” on some teams...but should there be?

    In this session, Diane evaluates the pros and cons of eliminating job titles and examines the concept of becoming a generalizing specialist. What does that really mean? What are the impacts to the team? Can you maintain your individual skills while your contributions to the team are getting blurred?

    Come and join in the discussion!

  • Liked Dave Nicolette
    keyboard_arrow_down

    Dave Nicolette - Automated Testing and TDD for Mainframe Applications

    Dave Nicolette
    Dave Nicolette
    Consultant
    Neo Pragma LLC
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Mainframe systems continue to play an important role in large IT operations. Contemporary software solutions often comprise components that run on multiple platforms, from smart phones and tablets to Windows, OSX, and *nix systems, and mainframes. 

    Is it feasible to extend modern software engineering practices like continuous integration; automated deployment; automated unit, component, and functional testing; and test-driven development to this venerable platform? It turns out to be quite feasible. There are several practical approaches to the problem, including commercial products from IBM and third parties; off-platform test drivers such as Cucumber, Concordion, and FitNesse; service virtualization products; on-platform approaches such as Java on zOS Unix System Services; hand-rolled mocking of CICS, DB2, and MQSeries resources; using IBM utilities to isolate and test individual steps from batch jobstreams; and isolated off-platform solutions based on hand-rolled test frameworks running under S390 emulation or mainframe-compatible compilers.

    This session provides a summary of several of these approaches. Unfortunately, it isn't feasible to run working examples on an actual mainframe in the context of the conference. We can show code that works and walk through it to illustrate approaches to test automation that are in use in real mainframe environments, and we can demonstrate the emulation-based solutions that don't require a connection to a real mainframe.

    To wrap up, we can have a group discussion about the specific testing and automation issues you have in your organization and how you might introduce test automation on your mainframe systems. Better yet, you can share your own stories of how you have solved this problem.

     

  • Liked DJ Daugherty
    keyboard_arrow_down

    DJ Daugherty - BYOD : Build your own drone… multi-rotor quadcopter that is!

    DJ Daugherty
    DJ Daugherty
    developer
    Pillar Technology
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    In this world of ever increasing opportunities to purchase ‘toys’ classified as ‘drones’… have you ever wanted to fly a drone? Have you ever asked yourself the question… should I buy a drone or build? This presentation will discuss why the term ‘drone’ should be most generally referred to as… ‘multi-rotor copter’ and not UAV (unmanned autonomous vehicle) or drone. This presentation will discuss the basics of how a multi-rotor works… the steps to build a multi-rotor… including details on flight controllers, frame selection, motors and props (including determining what type of multi-rotor will suite your purpose), speed controllers and batteries. There are a lot of variables… all of these details will be broken down, making the process of building your first copter a ‘flight in the park’. At the end… a flying multi-rotor copter will be air-worthy and demonstrated.