Sharing Our Passion for Technology
& continuous learning
  • default icon

    Delaying the Inevitable: Design Details

    “Decide as late as possible” On the surface this principle of Lean Software Development would seem to suggest that we, as engineers, should put off as many decisions as possible till the last moment. This seems counterintuitive, as creating a working piece of software requires a great deal of planning...
  • default icon

    Pro Tips for Onboarding a New Teammate

    Pro Tips for Onboarding a New Teammate Intro Last month’s blog post, Pro Tips for Joining a New Team, was from the perspective of the reader joining a team. But what if you’re a member of a team that is onboarding a new teammate? Look no further, we’ve got you...
  • An Agile team putting sticky notes on a whiteboard during a retrospective

    Retrospective on Holiday

    Lets face it, Agile Retrospectives, like all things, can get a little stale when they become too habitual. Maybe you're finding yourself in a rut answering the same old questions with the same old sticky notes, or maybe you're just looking for a fun twist on an already effective routine....
  • open planner with a phone and pen close at hand

    Dates and Deadlines in Agile: A Delivery Lead's Perspective

    In the world of agile sometimes dates matter, hold on let me finish. The day something goes to production should not be considered firm until closer to delivery. Stakeholders consider a date the date, but in reality, they are really hard to set. They are based on estimates, based on...
  • Two people discussing tests in front of a computer

    How My Team Uses Cypress for End-to-End Testing

    This blog is part of a series on end-to-end (E2E) testing in Cypress. In this post, we will take a look at how our team uses Cypress to benefit our workflow and increase the safety in which we deploy new features. This information is available in this presentation I give...
  • Repeated question marks

    Asking the Right Questions

    In a previous blog post, Brenda Peshak discussed the “Definition of Done”. As a team, we ran through an exercise to understand requirements and determine Minimal Viable Product (MVP). This got me thinking about real life examples of software and how decisions made by product owners and product managers directly...
  • Teammates sitting together and looking at code

    Node Reference - Koa

    Prerequisites This article builds on the prior article: Unit Testing. Shift Left DevOps Before we write code, we look at first principles. A key principle is: “shorten feedback loops”. We can acheive this by automating the steps leading up to validating what we’re building. This is one reason we focus...
  • Close-up of hand holding a compass

    Done The Game

    I recently presented on the topic of Definition of Done at our Monday Meetup. The purpose of the game was to help our teammates understand what “done” means. As a product owner, I hear a lot of keywords thrown around in the Agile Development process; Minimum Viable Product (MVP), Minimum...
  • Two men sawing wood on home improvement project

    Can You Use Agile Techniques with Non-Software Projects?

    As an Agile coach, I am always reflecting on my experiences and looking for ways to help others improve. Recently I hired a contractor to complete a home improvement project. It didn’t go very well. Let me share what went wrong and how I think using Agile techniques would have...
  • Teammates smiling and having discussion

    7 Ways To Go Beyond Your Agile Process

    Now that Agile has become mainstream, teams are looking to go beyond their Agile process to find ways to improve. There has even been recent use of the term “Antifr-Agile”, where process is secondary to product validation and customer learning (AgileDayChicago, 2016). Here are 7 ways that your team can...