• Johannes Brodwall
    Johannes Brodwall
    Niruka Ruhunage
    Niruka Ruhunage
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    Can you maintain agile engineering practices with a distributed team?

    Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

    In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

    After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

  • Liked Tarang Baxi
    keyboard_arrow_down

    A Practical Guide to Setting up Distributed Agile Projects

    Tarang Baxi
    Tarang Baxi
    Chirag Doshi
    Chirag Doshi
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

    • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
    • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
    • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
  • Liked Lynne Cazaly
    keyboard_arrow_down

    The Girl with the Chisel Tip Marker

    Lynne Cazaly
    Lynne Cazaly
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    One of the quickest ways to achieve greater buy-in, clearer communication and higher levels of engagement with team members, stakeholders, sponsors and business units is to get "visual agility". Using cards, stories, post it notes, visual charts, maps, models, metaphors - and most of all, some hand crafted "drawn-in-the-moment" visuals learn some engaging ways to facilitate with visuals in an Agile world. 

    Many people speak about 'making work visible' - showing progress, visualising solutions, scoping out possibilities - having visual agility gives you the skills to step into any role at a moment's notice and help bring clarity to the problem, quicker. This can apply to individual thinking and brainstorming, or group situations when you're presenting your idea or you're working with the group to create a solution. 

    Lynne Cazaly is a communications specialist and master facilitator. Lynne provides clarity to project complexity through workshops, training and visual strategy. Lynne trains, facilitates, speaks and coaches on visual facilitation, visual thinking and other engaging tools for project people, to help boost buy-in, collaboration and engagement.

    Lynne Cazaly is the author of the book 'Visual Mojo - how to capture thinking, convey information and collaborate using visuals'. 

    http://www.lynnecazaly.com.au/visual-mojo-the-book-lynne-caz/

    Included in this session is 30 icons to use straight away which Lynne calls 'Quick Pics'.

    Lynne recently ran the session again in New Zealand at an Agile Wellington Meetup - read their comments here

  • Liked Mikael Gislen
    keyboard_arrow_down

    Mitigating clashing paradigms between Agile Development and ISO 9000

    Mikael Gislen
    Mikael Gislen
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    There are, on a philosophical level, significant clashes between the agile paradigm and Quality Systems such as ISO 9000 or CMM/CMMi, this is already presented in the Agile Manifesto. Agile Development is based on what I would call post-modern paradigms when compared to the plan-driven and early iterative development methodologies which are based on a positivist paradigm.

    The underlying philosophical challenges cannot be easily mitigated. But a purist agile paradigm may tend to stress a positivist paradigm as well and this can be dangerous since then agile would not be agile any longer.

    While it may not be possible to completely remove the challenges between agile and quality systems, it is possible to learn to live with some tension between different paradigms. 

    There are some obvious areas of conflict, for examplethe Agile methodologies strongly discourages unnecessary documentation, and questions that it is possible to provide all requirements up-front. ISO 9000 on the other hand demands requirements up-front and documented evidence of almost anything, but such practical aspects can actually be mitigated with relative ease. Other aspects may demand much more effort. In particular the internal auditing process is problematic and other means of ensuring compliance may have to be considered.

    We have in my company systematically piloted a number of organisational changes in order to better support agile development. We have done this within the overall framework of our ISO 9000 system which is used a structure anda a gatekeeper. To do this we have used Action Research, which in it self is a kind of agile methodology, although of much older date than agile development.

    I will in my talk focus on the practical experiences we have had of building an organisational framework for agile development and while doing that suggesting a few means to mitigate the challenges mentioned initialy.

  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Advanced

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

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

  • Liked Ravi Kumar
    keyboard_arrow_down

    Evolutionary Approach for Maturing Agile Adoption in IT Services

    Ravi Kumar
    Ravi Kumar
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Change is a necessity and fact of organization sustenance and survival. Some changes are quite disruptive while others evolve gradually. Agile when compared to the many of the other models is radical and requires some fundamental shifts both in culture and traditional management practices. The Indian IT Services industry is at the crossroads of change with a heavy influx of agile projects in the recent past. Effective change in the context of agile with a heavy baggage from the past makes it harder. Business still has to continue and projects must be executed; so how do we go about an effective agile adoption/transition.

    This talk will try and look into the complexity and inhibitors of successful agile adoption in a typical large IT Services organization and questions the viability of certain agile methods such as Scrum and XP. We will explore why evolutionary methods such as Lean/Kanban are better fit and the necessity for evolutionary software development such as emergent design as a core premise for delivering Professional Software Development Services. Finally we also challenge the current status quo that is detrimental to a meaningful agile adoption and suggest few positive changes with Agile IT Services Manifesto.

  • Liked Andrea Heck
    keyboard_arrow_down

    Distributed Product Owner Team for an Agile Medical Development

    Andrea Heck
    Andrea Heck
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team. There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy. We need people who are good in two different fields of knowledge: medical and software development. As a third issues, the environment of the customers may be different in different countries.

    We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.

  • Liked Ram Ramalingam
    keyboard_arrow_down

    The secret shortcuts to Agile... (that won't get you there)

    Ram Ramalingam
    Ram Ramalingam
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    This is an exploratory talk, based, first, on some recent insights from cognitive science, behavioural economics (which have enriched Agile folklore already) and then on, some interesting twists from culture based research in sociology and psychology. While the former will be useful in understanding the common pitfalls encountered in a scaled Agile implementation, the latter, maybe useful in understanding the unexpected twists when doing scaled agile in a distributed/off-shore environment that have different cultural norms.

    While the anti-patterns and anti-paths are common across the world, the solution to these does differ. The assumptions behind what leads to a motivated, self-organizing, self-directing team will determine how to bring about a nuanced mindset to Agility, and understanding that what works in the West may not work in India (and other similar higher Power-Distance-Index countries).

    While sharing my experiences in a large scale Agile transformation and working with different cultures, I hope to bring out some subtle variations that could be useful in coaching and working with and transforming Agile teams in an offshore engagement.

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

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

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

  • Liked Carlos Lopes
    keyboard_arrow_down

    Multiple projects, different goals, one thing in common: the codebase!

    Carlos Lopes
    Carlos Lopes
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Are you developing new functionalities into branches? Have you ever experienced the pain of merging the changes into trunk? The so called "merge hell" is one of the first and probably the most important smell that tells you've been abusing of your source control manager branching capabilities and, most likely, hurting your productivity and your code quality as well. In order to move towards a continuous delivery approach, the practice of trunk based development suggests ways to avoid this type of issues among others like inconsistent feature sets, code that stays in an undeployable state for a long time, regressions introduced by semantic differences that arise during those joyful merging sessions, integration surprises with the other features, and the like. Even if you are not a developer on your team you will benefit from the examples and techniques presented.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Let's Kill an Agile Project

    Evan Leybourn
    Evan Leybourn
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Other talks and games will teach you how to run a successful Agile project. Only this one will teach you how to ruin an Agile project*. In this game we will break every Agile rule, disregard the manifesto and ignore common sense in the singular pursuit of failure (and fun).

    Each of you will be part of an Agile team with a dis-engaged Customer and micro-managing boss. Being Agile, there will be daily stand-ups, planning sessions, retrospectives, and kanban boards but nothing will go as you expect.

    * More importantly, this activity will teach you "how" Agile projects can fail and the reason behind many common Agile practices.

  • Liked Chad Wathington
    keyboard_arrow_down

    The Broken State of Process Improvement in Software Development

    Chad Wathington
    Chad Wathington
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Experimentation and the scientific method are very valuable for validating business opportunities. The Lean Startup and Lean UX are driving new thought patterns in the software development world. However, despite all the new thinking on product, rarely do organizations apply these techniques to their processes, opting for inefficiently adding more steps ad nauseum until productivity has ground to a halt. We’ll cover the following topics:

    • What are processes, and why do we need them
    • How processes affect delivery and productivity
    • Scale and process inefficiency
    • Process experimentation techniques
    • Designing productive processes
  • Liked Raj Anantharaman
    keyboard_arrow_down

    Cross Geo Collaboration and Delivery of Intel's Tablet - Scaled Agile and ALM Tools Story

    Raj Anantharaman
    Raj Anantharaman
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    We all know it takes a group of skilled engineers and developers to deliver any successful product. But what if they are all located in various geos, have different competencies / focus areas (hardware, software), on top of it - they are given a stringent deadline to deliver? In my session I'd like to share how Intel adopted the Scaled Agile framework and a homegrown "Managed Personal Accountability" (MPA) model to deliver the first tablet solution successfully. 

    It took a combination of good Agile planning and execution (Scrum of Scrums), an integrated ALM Toolset, along with performance management metrics of MPA to deliver this project successfully.

  • Liked Arlo Belshee
    keyboard_arrow_down

    Adopting Agile via Continuous Improvement - Your First 5 Days and Your Next 2 Years

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

    Do you adopt Agile all at once or one step at a time? What do you do after your adoption finishes (does that question even make sense)? What result should you expect at 30, 90, and 120 days? How do you get that? Is TDD the same on 20 days as at 360 days? Does it differ only in skill, or is it a completely different practice? We answer all these and a lot more. We show what you should expect for the first 2 years.

  • Liked Kevin Austin
    keyboard_arrow_down

    Scaling Agile Engagement

    Kevin Austin
    Kevin Austin
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    My talk is centred on doing better for our people; creating opportunities and building communities for a better life.

    I explore the actions and impact of a ground-up Agile Transition over the past 18 months, the challenges, what worked well, and how we began on a journey of connecting and growing Agile communities globally.

    A key theme discussed is our primary focus of putting the people we work with first while inspiring moments to challenge, learn, and explore new ways of thinking.

    • Scaling Agile Engagement is particularly applicable to anyone working with a large organization and/or distributed teams

     

     

  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Advanced

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

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

  • Liked Ravi Kumar
    keyboard_arrow_down

    Evolutionary Approach for Maturing Agile Adoption in IT Services

    Ravi Kumar
    Ravi Kumar
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Change is a necessity and fact of organization sustenance and survival. Some changes are quite disruptive while others evolve gradually. Agile when compared to the many of the other models is radical and requires some fundamental shifts both in culture and traditional management practices. The Indian IT Services industry is at the crossroads of change with a heavy influx of agile projects in the recent past. Effective change in the context of agile with a heavy baggage from the past makes it harder. Business still has to continue and projects must be executed; so how do we go about an effective agile adoption/transition.

    This talk will try and look into the complexity and inhibitors of successful agile adoption in a typical large IT Services organization and questions the viability of certain agile methods such as Scrum and XP. We will explore why evolutionary methods such as Lean/Kanban are better fit and the necessity for evolutionary software development such as emergent design as a core premise for delivering Professional Software Development Services. Finally we also challenge the current status quo that is detrimental to a meaningful agile adoption and suggest few positive changes with Agile IT Services Manifesto.

  • Liked Tarang Baxi
    keyboard_arrow_down

    A Practical Guide to Setting up Distributed Agile Projects

    Tarang Baxi
    Tarang Baxi
    Chirag Doshi
    Chirag Doshi
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

    • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
    • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
    • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
  • Corey Haines
    Corey Haines
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

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

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

  • Liked Chad Wathington
    keyboard_arrow_down

    The Broken State of Process Improvement in Software Development

    Chad Wathington
    Chad Wathington
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Experimentation and the scientific method are very valuable for validating business opportunities. The Lean Startup and Lean UX are driving new thought patterns in the software development world. However, despite all the new thinking on product, rarely do organizations apply these techniques to their processes, opting for inefficiently adding more steps ad nauseum until productivity has ground to a halt. We’ll cover the following topics:

    • What are processes, and why do we need them
    • How processes affect delivery and productivity
    • Scale and process inefficiency
    • Process experimentation techniques
    • Designing productive processes
  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Agile Anti-Patterns in Distributed Teams

    Pavel Dabrytski
    Pavel Dabrytski
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Implementing Agile is hard. You know what is even harder? Implementing Agile across distributed offshore teams.
    Due to constrains we face in our daily communication and collaboration, it is always difficult to get rid of old waterfall thinking. Sometime waterfall way even feels easier. This is where we find most of Distributed Agile Anti-Patterns.
    Agile Anti-Pattern often looks like Agile, it follows the right mechanics, but it is missing essential Agile values and principles.
    Join me for an interactive session where you will learn about 10 Agile Anti-Patterns specific to outsource and offshore development, and the ways to address them.

    Some of my favourite Anti-Patterns are:
    * Retrospective via emails
    * Scrum Master across the sea
    * Stabilisation sprint (sprint for bug fixing)

  • Liked Arlo Belshee
    keyboard_arrow_down

    Adopting Agile via Continuous Improvement - Your First 5 Days and Your Next 2 Years

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

    Do you adopt Agile all at once or one step at a time? What do you do after your adoption finishes (does that question even make sense)? What result should you expect at 30, 90, and 120 days? How do you get that? Is TDD the same on 20 days as at 360 days? Does it differ only in skill, or is it a completely different practice? We answer all these and a lot more. We show what you should expect for the first 2 years.

  • Liked Caleb Brown
    keyboard_arrow_down

    A Distributed Scrum Challenge: How We Turned Certain Failure into Success

    Caleb Brown
    Caleb Brown
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    What happens to a software product when its development is moved from Seattle to Chennai, its team is cut down to four people, and it is given to a first-time product owner located on the other side of the world from his team? Against the odds, and using Scrum and Agility, Nithya Thirugnanasundaram and Caleb Brown not only rose to the challenge, they doubled product sales and increased the renewal rate from 47% to 92%. In this experience report, you will learn the specific practices Nithya and Caleb used to overcome challenges such as communication, quality, tasking, interruptions – and never having met face-to-face. You will leave understanding the Agile practices that led this team to success, including having a strong commitment to practicing Scrum, being able to see completed work, and reviewing the UATs, as well as the vital roles played by the Scrum Master and Product Owner. 

  • Liked Dinesh Sharma
    keyboard_arrow_down

    Trust and Committment, a two point mantra for a successful agile projects in offshore

    Dinesh Sharma
    Dinesh Sharma
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Agile projects success (or failure) depends on two key points in an offshore setuo i.e. Trust and Commitment. Lack of either can cause serious trouble in agile projects as they say "You can't solve people problems with policies". So a lack of Trust on each other (Customer and Supplier) leads to rigid, complicated, lengthy SLA driven contracts and both side fight over it by taking oath of 'the contract'. Trust comes from knowing each other well and it takes some serious commitment to build trust. Committment from Customer should be is to treat its supplier more as partner or equal stakeholder in the project and invest in making a strong, trustworthy relationship early in the project to build a long lasting bond. Also, equally from a supplier committment is to understand its Customer challenge and help them to achieve their business goals. A committed supplier will invest in its people to produce a best quality product for its Customer and be transparent with their (and customer) organisation culture and its challenges and openly discuss how to overcome those. A bond based on Trust and Commitment goes a long way and bring a very healthy environment for people working in that environment.

  • Liked Kevin Austin
    keyboard_arrow_down

    Scaling Agile Engagement

    Kevin Austin
    Kevin Austin
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    My talk is centred on doing better for our people; creating opportunities and building communities for a better life.

    I explore the actions and impact of a ground-up Agile Transition over the past 18 months, the challenges, what worked well, and how we began on a journey of connecting and growing Agile communities globally.

    A key theme discussed is our primary focus of putting the people we work with first while inspiring moments to challenge, learn, and explore new ways of thinking.

    • Scaling Agile Engagement is particularly applicable to anyone working with a large organization and/or distributed teams

     

     

  • Liked Dinesh Sharma
    keyboard_arrow_down

    Offshoring Agile Projects - Myth, lies and Facts

    Dinesh Sharma
    Dinesh Sharma
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Offshoring in an agile environment (especially with Indian IT organisation) is always a hot topic within agile communities. You will often find people talk about challenges rather than opportunities with offshoring agile projects e.g.

    • communication challenge,
    • lack of focus on quality,
    • rigid offshore organisation environment,
    • lack of agile practice knowledge,
    • lack of trust etc.

    Although these constraint-cum-challenges often directly linked to offshoring but it can exists in a non-offshore environment as well. For example, to see how you can work effectively with distributed teams you don't need run a project in offshore environment, just split your teams and ask them to sit on a different floor without seeing each other face to face and all these so called offshore challenges will appear in an onsite environment as well.

    So lets understand various Myths, lies and facts about offshoring agile project and understand key ingredients to make it successful.

  • Liked Pooja Wandile
    keyboard_arrow_down

    The different engagement models, processes, challenges and solutions for a distributed Scrum Team in an outsourced product development (OPD)

    Pooja Wandile
    Pooja Wandile
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    A distributed Scrum team is a necessity than a choice in many cases. Often customers and their suppliers struggle to put up a team model that will work effectively and provide maximum value. The customer wants to be absolutely sure how the entire engagement will be executed so that there are no surprises later.

    So, what are the different ways of forming teams in a distributed environment, what is the impact on the execution, how do you execute different engagement models, what challenges do you see and so on? These are the questions the customers are interested in.

    This talk will focus on answering the above questions. We have defined 3 types of distributed team models and implemented in few of the projects in an onshore-offshore scenario. We have also tailored scrum meetings like planning, DSM, etc. so that these meetings are more effective in distributed model. While some of the changes have worked, some still needs to be enhanced further.

     

  • Liked Lynne Cazaly
    keyboard_arrow_down

    The Girl with the Chisel Tip Marker

    Lynne Cazaly
    Lynne Cazaly
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    One of the quickest ways to achieve greater buy-in, clearer communication and higher levels of engagement with team members, stakeholders, sponsors and business units is to get "visual agility". Using cards, stories, post it notes, visual charts, maps, models, metaphors - and most of all, some hand crafted "drawn-in-the-moment" visuals learn some engaging ways to facilitate with visuals in an Agile world. 

    Many people speak about 'making work visible' - showing progress, visualising solutions, scoping out possibilities - having visual agility gives you the skills to step into any role at a moment's notice and help bring clarity to the problem, quicker. This can apply to individual thinking and brainstorming, or group situations when you're presenting your idea or you're working with the group to create a solution. 

    Lynne Cazaly is a communications specialist and master facilitator. Lynne provides clarity to project complexity through workshops, training and visual strategy. Lynne trains, facilitates, speaks and coaches on visual facilitation, visual thinking and other engaging tools for project people, to help boost buy-in, collaboration and engagement.

    Lynne Cazaly is the author of the book 'Visual Mojo - how to capture thinking, convey information and collaborate using visuals'. 

    http://www.lynnecazaly.com.au/visual-mojo-the-book-lynne-caz/

    Included in this session is 30 icons to use straight away which Lynne calls 'Quick Pics'.

    Lynne recently ran the session again in New Zealand at an Agile Wellington Meetup - read their comments here

  • Johannes Brodwall
    Johannes Brodwall
    Niruka Ruhunage
    Niruka Ruhunage
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    Can you maintain agile engineering practices with a distributed team?

    Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

    In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

    After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

  • Liked Mikael Gislen
    keyboard_arrow_down

    Mitigating clashing paradigms between Agile Development and ISO 9000

    Mikael Gislen
    Mikael Gislen
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    There are, on a philosophical level, significant clashes between the agile paradigm and Quality Systems such as ISO 9000 or CMM/CMMi, this is already presented in the Agile Manifesto. Agile Development is based on what I would call post-modern paradigms when compared to the plan-driven and early iterative development methodologies which are based on a positivist paradigm.

    The underlying philosophical challenges cannot be easily mitigated. But a purist agile paradigm may tend to stress a positivist paradigm as well and this can be dangerous since then agile would not be agile any longer.

    While it may not be possible to completely remove the challenges between agile and quality systems, it is possible to learn to live with some tension between different paradigms. 

    There are some obvious areas of conflict, for examplethe Agile methodologies strongly discourages unnecessary documentation, and questions that it is possible to provide all requirements up-front. ISO 9000 on the other hand demands requirements up-front and documented evidence of almost anything, but such practical aspects can actually be mitigated with relative ease. Other aspects may demand much more effort. In particular the internal auditing process is problematic and other means of ensuring compliance may have to be considered.

    We have in my company systematically piloted a number of organisational changes in order to better support agile development. We have done this within the overall framework of our ISO 9000 system which is used a structure anda a gatekeeper. To do this we have used Action Research, which in it self is a kind of agile methodology, although of much older date than agile development.

    I will in my talk focus on the practical experiences we have had of building an organisational framework for agile development and while doing that suggesting a few means to mitigate the challenges mentioned initialy.

  • Liked Ram Ramalingam
    keyboard_arrow_down

    The secret shortcuts to Agile... (that won't get you there)

    Ram Ramalingam
    Ram Ramalingam
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    This is an exploratory talk, based, first, on some recent insights from cognitive science, behavioural economics (which have enriched Agile folklore already) and then on, some interesting twists from culture based research in sociology and psychology. While the former will be useful in understanding the common pitfalls encountered in a scaled Agile implementation, the latter, maybe useful in understanding the unexpected twists when doing scaled agile in a distributed/off-shore environment that have different cultural norms.

    While the anti-patterns and anti-paths are common across the world, the solution to these does differ. The assumptions behind what leads to a motivated, self-organizing, self-directing team will determine how to bring about a nuanced mindset to Agility, and understanding that what works in the West may not work in India (and other similar higher Power-Distance-Index countries).

    While sharing my experiences in a large scale Agile transformation and working with different cultures, I hope to bring out some subtle variations that could be useful in coaching and working with and transforming Agile teams in an offshore engagement.

  • Liked Carlos Lopes
    keyboard_arrow_down

    Multiple projects, different goals, one thing in common: the codebase!

    Carlos Lopes
    Carlos Lopes
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Are you developing new functionalities into branches? Have you ever experienced the pain of merging the changes into trunk? The so called "merge hell" is one of the first and probably the most important smell that tells you've been abusing of your source control manager branching capabilities and, most likely, hurting your productivity and your code quality as well. In order to move towards a continuous delivery approach, the practice of trunk based development suggests ways to avoid this type of issues among others like inconsistent feature sets, code that stays in an undeployable state for a long time, regressions introduced by semantic differences that arise during those joyful merging sessions, integration surprises with the other features, and the like. Even if you are not a developer on your team you will benefit from the examples and techniques presented.

  • Liked Andrea Heck
    keyboard_arrow_down

    Distributed Product Owner Team for an Agile Medical Development

    Andrea Heck
    Andrea Heck
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team. There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy. We need people who are good in two different fields of knowledge: medical and software development. As a third issues, the environment of the customers may be different in different countries.

    We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Let's Kill an Agile Project

    Evan Leybourn
    Evan Leybourn
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Other talks and games will teach you how to run a successful Agile project. Only this one will teach you how to ruin an Agile project*. In this game we will break every Agile rule, disregard the manifesto and ignore common sense in the singular pursuit of failure (and fun).

    Each of you will be part of an Agile team with a dis-engaged Customer and micro-managing boss. Being Agile, there will be daily stand-ups, planning sessions, retrospectives, and kanban boards but nothing will go as you expect.

    * More importantly, this activity will teach you "how" Agile projects can fail and the reason behind many common Agile practices.

  • Liked Prasad
    keyboard_arrow_down

    Distributed Agile 2.0

    Prasad
    Prasad
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    There is nothing ‘Agile’ in the current distributed Agile project management systems, which is focused towards passively capturing and providing information to teams, they are traditionally designed for people who have no choice but to use, which are ‘transaction oriented than ‘relationship oriented’ this is really ‘anti Agile’.

    This discussion / talk is inspired by Geoffrey Moore concept of systems of engagement . This discussion / talk is intended to

    a)      Provoke thought on how to bring ‘Agile’ values and principle in transitioning from current Agile project management system designed around discrete pieces of information ("records") to systems which are more decentralized, & relationship oriented which embraces social behavior of a team.

    b)    Talk also brings out following uniqueness of Systems of engagement and how can we achieve it in distributed Agile context

    Systems of Engagement – Distributed Agile 2.0

    Systems of Records ( current Agile project management)

    High complexity

    High volume

    Relationship oriented

    Transaction oriented

    Outgrowth of project teams

    Outgrowth of value

    Organize around orchestrator

    Organize around concentrator

    Focus : Expertise, innovation and market development

    Focus : efficiency, speed, and adaptability

     

  • Liked Anuradha Gajanayaka
    keyboard_arrow_down

    Some say they do Scrum to be agile ...

    Anuradha Gajanayaka
    Anuradha Gajanayaka
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    In the challenging context of offshore Agile Software Development, not everything in the book would work. In this experience report, I would like to discuss how the teams can tailor the current so called standard Agile methodologies/practices (within the guidelines of the Agile Manifesto), yet become successful in deliveries.

    In the session, I would like to discuss some of the agile practices the audience is using and then discuss the challenges they face when it comes to Agile Offshore Development. Then I would like to draw my experience on offshore software development projects where we successfully used Agile concepts and demonstrate how to customize those standard methodologies/practices within the Agile Manifesto Framework.

  • Liked Raj Anantharaman
    keyboard_arrow_down

    Cross Geo Collaboration and Delivery of Intel's Tablet - Scaled Agile and ALM Tools Story

    Raj Anantharaman
    Raj Anantharaman
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    We all know it takes a group of skilled engineers and developers to deliver any successful product. But what if they are all located in various geos, have different competencies / focus areas (hardware, software), on top of it - they are given a stringent deadline to deliver? In my session I'd like to share how Intel adopted the Scaled Agile framework and a homegrown "Managed Personal Accountability" (MPA) model to deliver the first tablet solution successfully. 

    It took a combination of good Agile planning and execution (Scrum of Scrums), an integrated ALM Toolset, along with performance management metrics of MPA to deliver this project successfully.

  • Liked Sudheer Kotagiri
    keyboard_arrow_down

    Automation of Engineering aspects in Agile Factory Model

    Sudheer Kotagiri
    Sudheer Kotagiri
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    With Agile, every aspect of software engineering needs to be done in a quick and consistent manner. Automation is one of them and we will showcase how various engineering  aspects like Unit Testing, Functional Testing, Integration, Build and Deployments were handled in “Agile Factory Model” with large-scale, distributed teams.

  • Liked Sarika Nagvekar
    keyboard_arrow_down

    Learn the knack of implementing distributed scrum in workplace

    Sarika Nagvekar
    Sarika Nagvekar
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Nowadays most of the projects have more than one team working on them also the team members are distributed at varoius sites.
     
    The knowledge of working with agile distributed team is essential in the current scenario.
    In this session We would like to focus on a case study for gaining more insights on how to scale and how to work with agile distributed teams.

    - Manage cordination with two or more teams.

    - Conduct iteration planning and syncrozise work, irrespective of the number of teams.

    - Probe the varoius challenges facing distributed teams and resolve them. (Example Lack of Communication, Minimum Team Overlap, Requirements Discontinuity, Cultural Barriers).

    - Achive good team allocation, how to interacte with team members, and how to coolaborate and choose the best meeting timings across all time zone.

    - Apply immediate practical advice, where ever the teams are distributed.

  • Liked Mark Shead
    keyboard_arrow_down

    Effective Communication With A Distributed Team

    Mark Shead
    Mark Shead
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Face-to-face communication is recognized in the Agile Principles as the best way for teams to convey information. However, not all teams can be co-located. Successful communication on distributed teams isn't just a matter of just buying the right technology. Teams with a strong communication culture will find a way to communicate well regardless of what official tools they are given. Poor communication cultures will do poorly even with state of the art tools.

    This talk is going to use specific examples to show how to enable effective communication and trust between team members distributed across different locations and timezones. While there will be some discussion of technology, the focus is on how to identify and foster a culture of communication on your team. 

     

  • Liked Jayathirtha Rao
    keyboard_arrow_down

    Structuring Enterprise Agile in a Traditional Delivery Organization

    Jayathirtha Rao
    Jayathirtha Rao
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    Indian IT services companies have built large organizations that are aligned to delivering projects with waterfall or similar methodologies. While Agile clearly delivers value to clients, it is important to ensure that delivery managers understand the benefits of Agile as well as have a roadmap to change their current structures to Agile.

    In large programs, we are increasingly seeing a conversion of waterfall teams to Agile. What does this mean for delivery managers who have successfully run their teams in waterfall mode? This is an important question to address else we will encounter (as we already do in many cases) resistance to Agile adoption from delivery management.

    In this session we will provide examples of how we have addressed the problems related to this conversion, including:

    -       How to recognize anti-patterns in an organization

    -       Handling matrix based management that leads to more leads and less deliverables (waste)

    -       Dealing with teams that build it, hand off and don’t support it

    -       Typical service company culture of rotating the best people out, and leaders who should look at results but look at interim tracking instead.

    We will provide real life scenarios covering:

    1. Typical distributed agile with multiple vendors – BAs with vendor 1, Dev in their own sprints with vendor 2, QA in their own sprints with vendor 3 – how can you do a vertical slice across a project rather than silos?
    2. Change budgeting and resource cycles from yearly cycles to smaller sprint aligned measures.
    3. Change metrics to output based on business value for tracking a program and portfolio, lower metrics should be for the team to measure progress and make improvements.

     

  • Liked Joe Zachariah
    keyboard_arrow_down

    Can India be truly Agile?

    Joe Zachariah
    Joe Zachariah
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    It's Indian Independence day today as I work on this proposal. As I read newspapers today, I understand the importance of the IT and ITES Offshore business, which has almost single handedly provided employment to millions of technically suave and English speaking folks. One question that repeatedly comes to surface is whether the Indian IT industry will be able to up its game from the servicing mentality which started the boom of IT in India. As Agile and Scrum began to become the flavour of the worldwide IT industry, many firms in India also went out on the Agile path, many of them out of pressure from their Western clients. Some of them were successful, but there are also numerous examples of failures of the Agile model and also half hearted adoptions, which have led Western businesses to believe that maybe India is not adept enough to take its game to the next level where teams can follow the Agile framework.

    My talk would be driven by my experiences of following Agile in different ways in my different teams over the last 6-7 years. My forays into the Agile ways of software delivery in India have been largely successful and I cannot see a reason why Agile will not work in India.

    In my talk, I would focus on the reasons on why Agile would work in India. Right from the way we approach diversity and inclusivity, to the way we approach our post election coalition party governance model, the Indian way of living is rife with finding innovative ways to quickly adapt to change, which essentially is the Agile mantra.

    I plan to start with a simple example. Of the Western way of cooking & dining as compared to the Indian way of cooking & dining. A traditional Indian kitchen is a sacred space. It is decorated with auspicious signs. Sometimes, it doubles up as a puja room. In many households, you are not allowed to enter the kitchen with footwear, you are expected to bathe before lighting the kitchen fire, you are not allowed to eat unless you have taken a bath - these can be metaphorically compared with the Ceremonies that an Agile team practising Scrum follows - the daily standups, sprint planning and reviews, etc. However the core delivery is the food. And no matter what ceremonies you follow and what your menu for the day is, the food comes out daily at the same time and is served everyday with the same set of stakeholders. There aren't as many tools and supporting equipment that you might see as in a Western kitchen, but at the end of the day the practices followed in a typical Indian kitchen are very Agile at heart.

    There are many other examples from Indian culture and mythology that one can refer to understand that Indians are essentially Agile at heart. Open source product groups, many of which are largely Agile, can also find a reference point in Indian culture and mythology. That which is timeless is referred to in the Indian context as Sanatan. It refers to wisdom that has no founder and is best described as collaborative and open source freeware. Every idea is accepted but only that which survives the test of time, space and situation eventually matters.

    There are many myths circulating in the IT industry that Agile cannot survive in India, since Indians cannot be trusted to be self governed and always require direction. Also Indians don't know how to have fun at work. Through my presentation I seek to dispel those myths drawing from Indian mythology and culture and essentially try to make folks understand that reasons for Agile not working in India is the same as Agile not working elsewhere. What you need to make Agile work at the end of the day, is just the belief that it will work.

  • Liked Shamira Dias
    keyboard_arrow_down

    GUIDING YOUR OFFSHORE CLIENT FROM WATERFALL TO AGILE: what works and how

    Shamira Dias
    Shamira Dias
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    A Scandinavian client who had bad experience with offshoring came to our doorstep. He was somewhat skeptical about offshoring but was willing to take a second chance. We had to be vigilant right from the start, it was a learning experience, a new project a suspicious customer and a watchful management… how did we handle the situation? The obstacles experienced by the team are universal. They are applicable to any team attempting to convert a client from waterfall to Agile.

     ss

     

     

    How did we initiate the project - what was the way forward?

    Were we cautions or did we plunge right in?

    Did we play by the rules or did we make our own?

     The learning experience of this talk is a step by step directive of how the above challenge was undertaken. The audience will be introduced to four attributes identified by the team as the four pillars of offshore agile rollout, namely being resilient, being innovative, being pro-active and being cooperative. By the end of the session the audience will understand

    (i)                 how to be resilient with the product owner, what are the essential practices

    (ii)               the habit of being innovative, what needs to be incorporated

    (iii)             the secret of pro-activeness, and taking control

    (iv)             the importance of being cooperative, how to instigate productive discussions

    Following this case study the audience will be able to apply the four pillars of offshore agile rollout to challenges faced with their own clientele.

  • Liked Manish Sinha
    keyboard_arrow_down

    Building High Performance Distributed Scrum Teams

    Manish Sinha
    Manish Sinha
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    (anonymous)

    Working with distributed teams is a necessity driven by globalization and outsourcing in today’s business world. Being effectively agile with these distributed teams is always a challenge. The challenges multiply when such teams consist of team members from different cultures working thousands of miles apart. Organizations are required to have teams that perform despite of challenges faced by such teams. They need to adapt to stay in business. But to get ahead in business, only adaptation doesn’t
    help, they need innovation as well.
    The session doesn’t cover any theoretical part of Agile but an “all practical”
    approach that has been tried, tested and verified. This session talks about how challenges with distributed teams can be transformed into opportunities for building high performance Scrum teams in distributed environment. The session shares best practices and lessons learnt with execution of Scrum in highly distributed team covering over seven different locations across geographies.
    The session will closely look at common challenges faced by distributed Scrum teams and how a simple restructuring of such teams can resolve many of these challenges. The session will put forward effective ways of building high team synergy in a cross cultural environment. The session will also cover few simple ways of using Lean techniques to identify potential improvement areas and to make impactful improvements.