This is an interview with Kevin Parker (@kevinparkerusa) about DevOps How do you see agile affecting application development and delivery? The biggest impact is that application development teams are using agile to speed up their delivery of software changes and updates. This makes the developers happy as they can get through requests faster. However, releasing … Continue reading DevOps Q&A with Kevin Parker
Author: Matthias Marschall
The opinions stated here are my own, not those of my company.
Lifecycle of a Click – Improving Web Page Speed
This is a guest post by Brian Doll, Application Performance Engineer at New Relic Six seconds can be an excruciatingly long time to wait for a single web page to load. Why does it take so long? Let's take a look at each step of the timeline and see how we can make it faster. … Continue reading Lifecycle of a Click – Improving Web Page Speed
Scrum Meetings – Relief or Burden?
Scrum defines a set of required meetings: Sprint Planning, Daily Scrum, Scrum Review, and Scrum Retrospective. Additionally, there might be a Scrum of Scrums, if you're running multiple Scrum teams in parallel. If you're doing two week sprints you spend at least half-a-day per week in Scrum meetings. Isn't that a lot of additional overhead? … Continue reading Scrum Meetings – Relief or Burden?
Scrum or Kanban – It does not matter
This is a guest post by Boris Gloger (@borisgloger) A couple of days ago I commented on Matthias' post about the myth that Scrum forces a team to release new functionality only after a sprint is finished while Kanban would is more flexible. I wanted to know the difference between Scrum and Kanban, and why … Continue reading Scrum or Kanban – It does not matter
The three essentials of any agile process
In the heat of introducing agile practices like daily stand-up meetings, retrospectives, unit testing, or defining "Done", you can get easily overwhelmed by all the new and shiny ideas. It's a real danger that implementing these new practices creates huge overheads, slows you down, and frustrates the team. They forget why you actually introduced agile … Continue reading The three essentials of any agile process
Scrum vs Continuous Deployment or why Scrum falls short for web applications
Product development needs consistency The basic idea of Scrum is to create a safe and change-free environment to enable a team to concentrate on the planned development tasks. The team plans out a sprint of typically two weeks and the idea is that they work uninterrupted during this period. This process really helps to get … Continue reading Scrum vs Continuous Deployment or why Scrum falls short for web applications
How to translate “business value” of things that are technically important
Agile teams often struggle with purely technical tasks. They just don't know how to translate technical necessity into business value. This makes it difficult to prioritize technical tasks against User Stories. In this article, I want to show you how to transform the hidden value of technical tasks into visible business value to ease prioritization … Continue reading How to translate “business value” of things that are technically important
How Digital Agile Management Tools Make You Blind (And How A Physical Kanban Board Can Help You See Again)
We've been using PivotalTracker for years to manage our agile software development process. It works like a charm for us. Whenever an idea comes up, we enter it into Tracker as an Epic (no matter how rough and abstract it might be). When the time comes to start implementing it, we usually break it down … Continue reading How Digital Agile Management Tools Make You Blind (And How A Physical Kanban Board Can Help You See Again)
Devops in a Regulated Mainframe Environment
Striving for real world experiences with agile, kanban, lean, and devops I ran a series of email interviews. Today I want to share the answers of Manu Khronis, NRB, Belgium. Please tell me a little about your current situation, your team and your job I am responsible for IT change management at Network Resource Belgium, … Continue reading Devops in a Regulated Mainframe Environment
Kanban: Changing story acceptance criteria whilst story is ongoing
In Scrum it's clear, a product owner can't change the acceptance criteria of a story in the current sprint without killing the sprint. Do you guys think the same principle should be applied in Kanban? I mean once a story has moved from a planning column and into an in-progress column, should the product owner … Continue reading Kanban: Changing story acceptance criteria whilst story is ongoing
