Loading…
Agile2017 has ended

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

DevOps [clear filter]
Monday, August 7
 

2:00pm

DevOps: an adoption model based on Maslow's Hierarchy (Nicolas Paez)
Limited Capacity full
Adding this to your schedule will put you on the waitlist.


Abstract:
DevOps is getting more and more popular everyday, its benefits sound very attractive. You want to give it a try but you don't know where to start. Maybe you already started but you are not sure how to continue. So this session is for you. It presents a model to fully understand the DevOps mindset and how to implement its associated practices. The model is based on an analogy with Maslow's hierarchy of needs and proposes a hierarchy of practices to adopt a DevOps strategy. As you may imagine you can not expect to work in a "DevOps-way" if you don't have some basic practices in place like continuous integration and retrospectives. So this model will allow you to identify your current location in the hierarchy and it will allow you to design a clear path through the hierarchy of DevOps practices.

Learning Outcomes:
  • * Understanding of the different practices involved in any DevOps initiative
  • * Assessment tool to identify your "actual location" in the hierarchy
  • * Strategies to incrementally "move" through the hierarchy of practices to embrace a DevOps mindset in your organisation

Attachments:

Speakers
avatar for Nicolas Paez

Nicolas Paez

Profesor, UBA & UNTREF
I am a software engineer with several years of experience in software development. I love teaching, I teach software engineering at the university. I work as an independent software engineer helping teams to adopt technical practices.I do believe that the main complexity in creating... Read More →



Monday August 7, 2017 2:00pm - 3:15pm
Wekiwa 9&10
 
Tuesday, August 8
 

9:00am

A Better, Faster Pipeline for Software Delivery (Gene Gotimer)
Limited Capacity seats available


Abstract:
The software delivery pipeline is the process of taking new or changed features from developers and getting them quickly delivered to the customers by getting the feature deployed into production. Testing within continuous delivery pipelines should be designed so the earliest tests are the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing lead to increased confidence that the code is a viable candidate for production and that more expensive tests—be it time, effort, cost—are justified. Manual testing is performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to serious problems progressing far down the pipeline before they are caught.
Be prepared to discuss your pipeline, automated or not, and talk about what you think is slowing you down and what is keeping you up at night. In this interactive workshop, we will discuss how to arrange your tests so each round provides just enough testing to give you confidence that the next set of tests is worth the investment. We'll explore how to get the right types of testing into your pipeline at the right points so that you can determine quickly which builds are viable candidates for production.

Learning Outcomes:
  • Each attendee should leave with a better understanding of their current and desired software delivery process.
  • The pipeline is about building confidence that the software is a viable candidate for production. Or realizing as early as you can that it isn’t.
  • Do just enough of each type of testing at each step in the delivery pipeline to determine if further testing is justified.
  • Different stages of the pipeline are for learning different things about your delivery process. Use them appropriately.
  • Do the most expensive tests last. Those are often the manual or subjective ones.
  • The pipeline offers a lot of opportunities to do tests that you might not have done if you had to set aside an explicit block of time to do them.

Attachments:

Speakers
avatar for Gene Gotimer

Gene Gotimer

Senior Architect, Coveros, Inc.
Gene Gotimer is a senior architect at Coveros, Inc., a software company that uses agile methods to help customers build software better, faster, and more securely. They do this by focusing on agile development and DevOps practices such as continuous integration, repeatable builds... Read More →


Tuesday August 8, 2017 9:00am - 10:15am
F4

2:00pm

CANCELLED: DevOps Transformation: The next step in Agility (Taghi Paksima)
Limited Capacity seats available


Abstract:
DevOps is more than just “dev” plus “ops”. It entails a mind-set shift to embrace the culture of continuous improvement, systems thinking and continuous delivery of business value across the whole value stream and affecting most of the organisation. In this workshop we will be collaboratively explore some of the core tenets of DevOps, primarily as a cultural and organisational transformation. The workshop will help participants gain insight into some of the basic, yet powerful, principles and practices of DevOps, such as streamlining flow of value, continuous delivery, and continuous feedback.

Learning Outcomes:
  • Experiment (through gamification) how DevOps practices and principles can help reduce time-to-market and decrease delivery pain.
  • Learn about DevOps transformation as an extension to Agile and how it will contribute to creating high-preforming organisations.
  • Understand some of the core cultural principles and technical practices of DevOps.
  • Learn about effective habits of DevOps teams to pick and the pitfalls to avoid.


Speakers
avatar for Taghi Paksima

Taghi Paksima

Agile Coach/Agile Engineering Consultant, improuv


Tuesday August 8, 2017 2:00pm - 3:15pm
H3
 
Thursday, August 10
 

10:45am

CANCELLED: Defining the MVP for an Agile Continuous Deployment Strategy (Elizabeth Woodward)
Limited Capacity seats available


Abstract:
Come learn how you can use the concepts of Minimum Viable Products (MVPs) and build-measure-learn feedback loops to focus your team’s continuous improvement efforts. Popularized by Lean Startup, an MVP is a version of a new product that uses the least amount of effort to gather a maximum amount of validated learning that can help with decisions about further investment. You’ll have a chance to establish continuous improvement backlog along with a tailored continuous improvement MVP that can potentially take your team from being “somewhat agile” to “agile with continuous deployment.”
This workshop begins with a quick overview of Lean Startup concepts and introduces the case study team that serves as the example referenced after each hands-on activity. Working as part of a small group, you will focus on a “Think Big, Start Small” strategy. You will establish a tailored full continuous deployment pipeline, identify desirable principles and practices for the different stages of the pipeline and identify the tooling required to support targeted practices. From there, you will create a rank-ordered backlog and establish an MVP. We will discuss setting up your Build-Measure-Learn loop, establishing your “value hypothesis,” defining your approach for baselining and measuring your experiment and, given examples, formulating decisions as to whether to “pivot or persevere.”

Learning Outcomes:
  • Establish a "to be" state for a continuous delivery pipeline, including stages, principles and practices and technology and tooling
  • Create a rank-ordered continuous improvement backlog that can take your team from agile to continuous deployment
  • Select a Minimum Viable Product from a rank-ordered continuous improvement backlog
  • Baseline and measure improvements that serve as the MVP for your continuous improvement backlog

Attachments:


Thursday August 10, 2017 10:45am - 12:00pm
F2