Agile | Mogital

Should your project use a Value-Driven approach, Plan-Driven approach or both?

This article originated from numerous discussions on when to use a Value-Driven approach, Plan-Driven approach or both. The practices in both approaches are not totally mutually exclusive, particularly in complex projects: there will always be a need for an appropriate level of governance, a plan and some things will need to happen in order. Each

BY @BarryAgile IN Agile, Lean, Value Driven Agile, eXtreme Programming (XP), Kanban, Lean, Lightweight, Management, PRINCE2®, Scrum, Waterfall

Why Measure Lead & Cycle Time?

This article covers some common questions on the purpose of Lead Time and Cycle Time measurements in software development. Lead Time and Cycle Time means different things to different people, depending on when the clock starts, team purpose and industry, so let’s be specific on what states or steps can be measured, with the Definition

BY @BarryAgile IN Agile, Development, Kanban, Lean, Management, Team Agile, CycleTime, Kanban, LeadTime, Lean, Visualise, Workflow

Leading Agile Teams in Practice

There are many ways to lead multiple Agile Teams, with some approaches being more effective than others. The Agile police may caution me after reading this (which I’ve preemptively created solidarity hashtags for), so to be clear: this article describes one tailored approach to leading multiple teams to deliver a technically complex product using Agile

BY @BarryAgile IN Agile Agile, Kanban, Lean, Lightweight, Management, Scrum

Is your team really Agile or mini Waterfall?

We have all heard it before: a team states with some confidence how Agile or Lean they are, maybe because they work in iterations (or sprints), manage their work on task boards or both. However, what is often unclear and usually controversial is, are they really practicing Agile or are they mini Waterfall or ‘Wagile’? We

BY @BarryAgile IN Agile, Development, Extreme Programming (XP), Kanban, Management, Planning, Scrum, Team, Waterfall

Should defects be estimated?

Within a development iteration or sprint, ensuring a story meets its acceptance criteria and passes its test case should be part of the story estimate and the Definition of Done. If a number of defects are identified after the iteration where the story was completed, e.g. identified during Regression Testing of the entire product in

BY @BarryAgile IN Agile, Development, Estimation, Extreme Programming (XP), Kanban, Management, Planning, Scrum, Team

Why JIRA is best for managing tasks on larger projects

There are dozens of popular tools currently being used to help manage Agile projects. For managing tasks on large or complex projects, however, JIRA has proven to be a more useful tool than than Trello. This is for a number of reasons, which are not limited to the following. Swimlanes – Trello does not have Epic, Assignee,

BY @BarryAgile IN Agile, Agile Tools, Case Study JIRA, Team, Trello

Can Trello be used to manage large Agile projects?

There are dozens of popular tools currently being used to help manage Agile Projects. One of these tools is Trello, a simple, intuitive task board that allows users to quickly add cards or tasks to a ‘To Do’ column or ‘Backlog’. In a recent project, a Trello board was used to create: Multiple backlog columns – Infrastructure,

BY @BarryAgile IN Agile, Agile Tools, Case Study, Development, Planning Agile, JIRA, Team, Trello

An Agile war story: why teams need to value upfront thinking

Passing a course and being coached is great. However, the real learnings come from the tailoring of good practices from methodologies to real projects. Being a real practitioner cannot be gained from a qualification alone, so we practice and learn lessons. Below is a summary from a recent CMS migration project for a large magazine

BY @BarryAgile IN Agile, Case Study, Estimation, Planning, Team Agile, CMS, Scrum, Team