Agile + DevOps Virtual 2020 - Agile Development
Before You Go!
Don't Miss Special Offers and Program Updates Straight to Your Inbox (Opt-Out at Any Time)!
Wednesday, November 11
Investing in Quality to Increase Velocity: Leveraging Automated Testing to Speed Up the Software Development Lifecycle
Everyone wants to develop software quickly, but there is a valid concern that increasing velocity may decrease quality. At Indeed, we set a company-wide goal to double velocity of our software development without hurting the quality of our releases. To accomplish this goal, we looked at each stage of the software development lifecycle and found which parts took the most time. Deployment and verification in our QA environment was one of the biggest bottlenecks and was due to our historic reliance on human quality assurance testing for each release. To alleviate this bottleneck, we wanted to...
_0.png%3Fitok=VxcOnQGH&sc=bcc7891d19ed357fdfd8e5faa29d7421 "Abraham-Marin")
Maximise the benefits of remote working with better Pull Requests
PreviewThe demands of the modern workplace are changing. Trends like flexible hours, remote working, or “bleisure” travel are being introduced to give employees more work-life balance. Moreover, organisations that are capable of working remotely in an effective manner are more resilient to external shocks, like the recent Coronavirus outbreak showed us. In order to remain effective when workers aren’t in the same place at the same time, teams need to leverage coordination tools. For the case of developers, one of the most important of these tools is the Pull Request. Join Abraham to...
The Recipe - Baking a diverse set of ingredients into a tasty integrated system
PreviewChallenge: At Intel each of the various software and firmware teams had independent source code management and CI systems. Consequently the product system integration teams had no consistency from the ingredient software and firmware teams requiring manual over head during system integration. This presentation will discuss how we addressed this by creating a common recipe for the ingredient software and firmware teams to follow. It will discuss what tools from the industry we used (Git, Jenkins, Artifactory) and what tools we had to create (Web Portals, Build Scripts). It will also...
Thursday, November 12
Code Review Practice for Empathy with Egoless Programming
PreviewWe will prepare code for code review and progress sheets and assessment template, and role cards for the participants. (Please check attachments.) We want to share that code review is not heavy and authoritative thing, but it is fun and can help participants understanding of business logic and improve their development skills at the same time. This practice is hands-on, and this practice has been used and spreading in our company since 2017. This code review practice will lead participants to become interested in code review. Participants will learn how to code review in a fun...
Using failure to successfully deliver software
Failure is feedback and feedback is the breakfast of champions, or in this case software delivery teams. How do software delivery teams “welcome changing requirements, even late in development“ while maintaining "continuous attention to technical excellence"? The answer is simple, through feedback, early and constant feedback. So why is it so hard to accept feedback? If feedback is so important why don’t we welcome it as early as we can and as often as we can? Many times it can be the delivery if you’re not asking for feedback it can come across as negative or as criticism. Fortunately,...
Metric-driven CI Stability
PreviewWhen I joined our Developer Experience team, we had very little visibility into how we were serving other engineers with our CI tools. We had no hard-evidence to back up any claims. We identified what we could and should measure. Then we established SLIs/SLOs to formalize those concepts and conducted an experiment to improve Buildkite stability. In the end we reached our goal on stability going from ~95% to 99.5%+ of builds that didn't fail because of something we had control. Now that we have hard data around the job we are doing, we don't have to make a decision about when to...