Nebraska.Code() Sessions tagged agile

Being an Agile Dev

Organizations talk about becoming agile but what does it mean for a developer to be Agile?

In this talk you’ll learn about scrum and other types of agile software development and what the differences are. And then we’ll take a deeper dive into scrum and why standups are more than just making sure you’re doing work, and why retrospectives are more than just talking about feelings. Along the way we’ll discuss what you should be contributing, and what you should be getting out of each meeting.

Speaker

Courtney  Heitman

Courtney Heitman

Scrum Master & UX Developer, Gallup

Easing Into Continuous Deployment

Have the confidence to deploy on Friday afternoon? I've definitely been places where doing so would make everyone cringe. Lets talk about some lightweight tools and processes to greatly reduce that risk. We'll discuss feature flags, trunk based development, pairing on critical sections, and other ways to help you have confidence in your deployment pipeline.

Speaker

Seth Larson

Seth Larson

Engineering Team Lead, Raven Industries

Test Driven Development: Back to the Basics

Test Driven Development (TDD) is a highly recommended but seldom utilized agile development practice. Primarily originating and associated with Extreme Programming, TDD is often misunderstood and therefore left by the way side when agile teams get going with development. I want to go back to the basics of TDD and show why it should be a practice every team employs. In Design Studio and Senior Design, we manage nearly 40 projects with more than 200 student team members combined. Test Driven Development can greatly impact these students’ careers in software development once they have realized its power and taken advantage of its benefits. Let’s bring it back down to the basics to remind you of this great opportunity.

Speaker

Jeremy Suing

Jeremy Suing

Design Studio Project Manager, UNL - Raikes School

Personal Kanban

Join me for a quick review of the major concepts presented in Jim Benson's foundational book, Personal Kanban. We will start by reviewing the two simple rules of Personal Kanban: 1) Visualize your work, and 2) Limit your work-in-progress (WIP). Then we will cover other important topics from the book, including establishing your backlog, what is value stream (or how to organize your Kanban Board), what it means to pull work through the process, and how to embrace kaizen (a state of continual improvement). The goal is to give you enough information to get you started down the path to using Kanban to manage your own personal tasks and projects.

Speaker

Keil Wilson

Keil Wilson

IT Enterprise Business Applications Architect, Nelnet

Agile Doesn't Work for Us - Agile in Infrastructure Teams

Infrastructure and support teams spend most of their time responding to emergencies. Trying to put support requests and incident tickets into iterations is ridiculous. Agile just doesn’t work for infrastructure teams! Or so we're told. This session will review the year-long implementation of agile/DevOps on an infrastructure team that supports 44 separate applications in a company with thousands of employees.

Attendees will learn how this team used and adapted Kanban to manage support queues and improve both the coverage and quality of support for their customers. We will also discuss how the team adopted Scrum to manage the project work that often takes a back seat to the urgent requests that regularly flood into support organizations.

There will be plenty of time for session attendees to ask questions, and discussion of issues will be encouraged.

Speaker

Keil Wilson

Keil Wilson

IT Enterprise Business Applications Architect, Nelnet