Home » Agile

Agile

Processes…

It has been a lot of talk about processes in the Jakarta and MicroProfile community lately, so I just want to remind us all about this item from the Agile Manifesto. Individuals and interactions over processes and tools. https://agilemanifesto.org/ That said, some process is needed. Especially for work with specifications. In this post, I explain the Jakarta EE Specification Process ...

Read More »

Does Your Team Need Minimum WIP Limits?

I spoke with an agile coach whose team works in flow, similar to this board. They don’t use iterations—they plan on demand. The column on the left, “Stories to Workshop” is their backlog refinement column. Recently, the team decided they need “minimum” WIP (work in progress) limits. Especially on the Workshop column. Why? Their product owner doesn’t spend enough time ...

Read More »

Agile Approaches Can’t Save Impossible Projects: Fixed Cost, Scope, Date

You’ve got an impossible project. You have no flexibility. The project is a fixed-price, fixed-scope, fixed-date project. And, you have a specific team to do the work. (There are other impossible projects. Such as when you have a collection of people who multitask among several projects.) Can an agile approach save these projects? No. An agile approach might help you see ...

Read More »

A Programmer’s Guide to Agile Implementation

Agile methodology is the most sought after software development model today. It promotes continuous iterations in development and testing. Agile is about going fast, releasing often, and working toward the real needs of the users.When it comes to businesses where the requirements are unpredictable, agile should be the go-to methodology. The core values of agile development are:  individuals and interactions ...

Read More »

Consider Product Options with Minimum Outcomes

Do you have trouble fitting “all” of the necessary work into an iteration? Your managers might want to push you to do more. Or, the product owner thinks you can do more. Or, the team wants to do more (see Beating a Team’s Goal.) Agile approaches are not about doing more. Agile approaches encourage us to do the least we ...

Read More »

5 Patterns for Effective Communication in Agile Teams

The way we communicate is the single most important skillset employers look for when hiring. It has a significant impact on cost, productivity, team morale, and employee retention in the workplace. A study conducted by The Economist shows that problems in communication often delay project completion, lead to low morale and missed goals, and can result in a loss of ...

Read More »

Thinking About “Beating” a Team’s Goal

Shaun’s comment on Measure Cycle Time, Not Velocity suggested a team might be better off measuring both cycle time and velocity. Why? For two reasons: “Beating” the last sprint goalAssisting the PO in a forecast of when things might be done. Let’s examine these ideas. Clarify Story Points Why even bother with story points? (If you haven’t read the original ...

Read More »

What Decision Will You Make Based on This Data?

Does your team have to keep two sets of “books”? You have an agile roadmap to see where you’re headed. You have a smallish backlog of the near/upcoming work. You’re delivering on a frequent basis. And, someone on your team keeps a Gantt chart because a manager wants to see the team’s progress in a form they feel comfortable with. ...

Read More »