Conference Time
Local Time

Big Apple Scrum Day 2015

Mon, Jun 1
Timezone: Asia/Kolkata (IST)

    Registration - Breakfast - 45 mins


    Gather in the Auditorium - 10 mins


    Introduction - 20 mins

  • Added to My Schedule
    Daniel Mezick

    Daniel Mezick - KEYNOTE: Successful Agile Adoption Using Open Space

    schedule  10:30 - 11:10 AM IST place Paul Callelo Auditorium star_halfRate

    Open Space gatherings arranged inside organizations are totally unlike the Open Space events you may be familiar with during public conferences. As described in the book SPIRIT from Harrison Owen, Open Space is actually designed to enable development and transformations in organizations. This session is about how to leverage Open Space to scale Agile across the enterprise.

    At the root of effective Agile is the self-managed team...a self-organizing system. At the core of Open Space is the power of self-organization. In this sense, effective Agile adoptions and Open Space are very, very similar.

    During this session I will present narratives, pictures, videos and testimony from C-level people as well as team members. Each will describe how Open Space inside their Agile adoption literally changed their lives. Of particular interest are the stories executives tell about how they learned to let go and trust their people to provide everything the Agile adoption needed to succeed at scale.


    Break - 20 mins

  • schedule  11:30 AM - 12:30 PM IST place Paul Callelo Auditorium star_halfRate

    You often hear people ask, "Does the ScrumMaster role need to be a full-time role?". Obviously, the answer is yes. And you can point to results that you should expect to see from teams served by full-time, dedicated ScrumMasters. And you can detail the different aspects of the role that require such dedication. But the root of the issue is a misunderstanding of the ScrumMaster role.

    One the surface, the ScrumMaster role is relatively simple; to serve the team by removing obstacles, facilitating meetings and coaching. Dig deeper, and the role becomes far more nuanced. The ScrumMaster role is one of nurture and change.

    This session analyzes the ScrumMaster role through the lens of choice as an outcome. That is, that the role of the ScrumMaster is to facilitate the choice of an individual to be agile. The role of the ScrumMaster is to enable the behaviors that lead to agility, within the team and the organization.

  • Added to My Schedule
    Mariya Breyter

    Mariya Breyter - Agile coaching is dead. Long live Agile practicing!

    schedule  11:30 AM - 12:30 PM IST place Ante Room star_halfRate

    For years, Scrum/Agile coaching has been an attractive career for many. It is frequently viewed as a continuation of a career for an experienced Scrum Master who understands the intricacies of the cultural change that makes Scrum teams successful, knows nuts and bolts of a Scrum engine, and has natural aptitude for knowledge sharing and growing others. A leader who is unselfish and acutely self-aware, who has experience, and ability to influence others.  Many Scrum practitioners saw this role as their next step in professional development. The 2010 book, Coaching Agile Teams by Lyssa Adkins’ and her Agile Coaching Institute made Agile Coaching a discipline rather than a buzzword. Now, five years later, Agile Coaching is rapidly losing its attractiveness as a professional career. In her open-space style talk based on a retrospective with the session participants, Mariya Breyter will explore why this is happening and what a natural career progression for an Agile coach is. Agile Coaches and Scrum practitioners will exchange their experience and discuss their paths for professional development.

  • Added to My Schedule
    Darren Taylor

    Darren Taylor - Lego Scrum

    schedule  11:30 AM - 01:00 PM IST place Club Room star_halfRate

    Lego Scrum will provide an interactive learning experience enabling participants to learn about Scrum by seeing it in action.

    Who should attend? Anybody wanting to increase their knowledge of Agile and Scrum, it’s non-technical  and is designed to be understood by everyone. 

    These sessions represent what Macmillan Science and Education conduct regularly throughout their business to help build a wider understanding and awareness of Agile and Scrum.

  • Added to My Schedule
    Tristan THEVENIN

    Tristan THEVENIN / Dana Pylayeva - Do the right thing with Story Mapping, do it right with SCRUM.

    schedule  12:35 - 01:05 PM IST place Paul Callelo Auditorium star_halfRate

    User story mapping is a useful technique which helps the teams with a product backlog visualization.             

    It enables a Product Owner to carry on discussions with business stakeholders and development teams at the appropriate levels of granularity.

    It helps the team to identify and build “vertical slices” of the system every Sprint, simplifies MVP and a release planning.


    In this session, we will give a short user story mapping primer and highlight the advantages of using this approach over the traditional flat backlog.

    Using FeatureMap tool as an example, we will demonstrate how user story mapping can be successfully applied in a distributed team environment.

    In this experience report we will demonstrate story maps created for software products as well as the story map we built for Big Apple Scrum Day.

  • Added to My Schedule
    Christine Novello

    Christine Novello - Translating Agile for a Non-Technical Team

    schedule  12:35 - 01:05 PM IST place Ante Room star_halfRate

    Parlez-vous Agile?

    Sprechen sie Scrum?

    Agile methods originated in technical practice, and its roots are solidly planted in the fertile ground of software engineering. Certifications in Scrum all require understanding of engineering practices, and the more senior level certifications require both in-depth understanding and practical application.  The message would seem to be that Agile practitioners must be Software Engineering practitioners. However, non-technical teams are adopting agile methods as ways to better organize – or, more accurately, self-organize – in increasing numbers.

    As the language and history of agile is so strongly steeped in software engineering, applying agile methods in a non-technical setting requires some translation to be applied in a non-technical team.  I'm not just talking about jargon translation here; the methods and practices themselves sometimes need a tweak to work outside software engineering. The use of agile and scrum is not a slam-dunk success in every setting - be it technical or non-technical - but in this talk, I will separate myth from reality and give some practical examples from my own experience.  I invite you to join to learn, to contribute, and to discuss the opportunities as well as the effort required to leverage Agile/Scrum for a non-technical team.  


    Lunch - 55 mins

  • schedule  03:05 - 04:05 PM IST place Paul Callelo Auditorium star_halfRate

    If you’re practicing scrum, you’re probably well versed in velocity, escaped defects and other common scrum metrics.  This presentation starts with a review of essential scrum metrics, how to properly use them, and how to interpret their trends.  We’ll then quickly pivot into advanced and emerging metrics that many scrum teams (and programs) have found beneficial - examples include: how to measure and quantify the cost of delay when your team is blocked, how to ensure your team is investing the right amount of time to maintain clean code and create automated test scripts, and how to assess that your team is sharing work to support the whole-team approach.  We’ll review a comprehensive taxonomy of scrum metrics and show examples of presented metrics in use.  We’ll conclude talking about opportunities to better empower scrum teams to self manage by integrating economic and budgetary data with scrum metrics - consider this example: rather than reviewing estimates & actuals for all the stories completed in a sprint, determine your team run rate and track the cycle time for each story completed, then use these two data points to compute the cost for each story completed during a sprint, finally ask yourself if your customer or sponsor would be happy with the amount they invested to complete each story - if you’ve never tried this type of economic analysis with your team, trust me, you’ll have a much different (and probably more effective) discussion.  By attending this session, participants will learn a comprehensive list of metrics and practices to gain greater insights to team / project health and reduce delivery risk - participants attending will receive a metrics worksheet that will list all metrics presented and include why and how to track each of them.

  • schedule  03:05 - 04:05 PM IST place Ante Room star_halfRate

    Do you remember the frustration that comes from trying to make traditional HR instruments like performance reviews work for your Agile teams? Do you feel HR is undermining your best efforts at collaborative leadership and is holding you back? Do you find yourself in a constant dispute with HR over people processes?

    It is inevitable: HR must embrace Lean | Agile values and principles in order to engage and energize Agile talents. It’s time to show HR how key people challenges like retention, talent development, and performance management can be addressed successfully with Lean | Agile.

    Join this session to

    – gain valuable insights into the world of Human Resource Management

    – recognize the impact of Agile HR practices through stories and examples

    – discover why Agile needs HR and vice versa

    – identify compelling arguments and tactics to convince HR to go Agile.    

  • Added to My Schedule
    David Horowitz

    David Horowitz - Distributed Scrum -- Why It's So Difficult and What We Can Do About It

    schedule  03:35 - 04:05 PM IST place Club Room star_halfRate

    Everyone knows that scrum works best when the entire team is sitting together in the same office. But the reality of today's working world is that more and more teams are geographically distributed. In many cases, this is the result of "strategic priorities" from senior management and is entirely inflexible. As scrum practioners, we must come up with strategies for adapting scrum to a distributed world. This talk will take a hypothetical distributed scrum team from release planning all the way through to launch day. What are some of the problems that will come up? What are the best ways of overcoming these issues? How should Scrum Masters facilitate sprint planning, sprint reviews, and sprint retrospectives? 


    Break - 15 mins


    Conclusion - 20 mins