seen from Sweden
seen from Russia
seen from Canada
seen from Singapore
seen from United States
seen from Netherlands
seen from Russia
seen from Chile
seen from Brazil
seen from Canada
seen from Tunisia
seen from United States
seen from Venezuela
seen from Russia
seen from United States
seen from Germany
seen from Malaysia
seen from Germany
seen from United States
seen from United States
Unite or Fail: Building a Culture of Respect Between Product and Tech
A culture of respect between product and tech is the foundation for lasting success in digital organisations. Without it, even the clearest separation of the what and the how breaks down into conflict, mistrust, and stalled delivery. We’ve already seen in No One Leads, Everyone Drifts: The Danger of Mixed-Up Roles how blurred boundaries erode clarity. But once those boundaries are clear, the real…
Debunking the Myths: Why This Isn’t Just Waterfall in Disguise
Waterfall in Disguise is a phrase that gets thrown around whenever agile, iterative, or hybrid ways of working don’t look “pure” enough. But calling everything that isn’t perfect agility “just Waterfall in disguise” misses the point and undermines progress. Let’s unpack why. Myth 1: Because We Plan Ahead, It Must Be Waterfall Yes, agile teams plan. They need roadmaps, forecasts, and release…
The importance of making faster, more confident decisions now
The importance of making faster, more confident decisions now
As the situation evolves, the ability to assess a range of potential scenarios quickly to maintain business continuity or competitive advantage is vital.Read More
View On WordPress
Maintenance Planning System
Components of a Project
So the next thing I will be blogging about is maintenance planning. I will create an PDF infographic document that will create a graphic road map for maintennace planning. This will endeavour to cover all aspects of the components that are required create an effective maintenance strategy. Although this will primarly look at maintenace planning in the oil industry…
View On WordPress
Agile Summary
Agile is a new type of planning system and would not be relevant or the correct system to be using for all projects. There are many industries that it would not be useful and where a clearer and more accurate planning system is required.
I understand that it is trying to cover an industry, mainly the software industry, which has been difficult to plan for in the past. It does what it says…
View On WordPress
Avoiding Agile Stereotypes
Sometimes with newer Agile teams, you’ll hear them say, “We don’t plan because we’re Agile.” This causes a lot of confusion with the rest of the organization. They’ll justifiably ask the question, how can you run a project without any planning? The truth is, you can’t.
Agile does have planning, it’s just different from traditional project management planning. The planning rules are there,…
View On WordPress
Producing Acceptable Documentation
One of the sticking points with new Agile teams is deciding what is considered acceptable documentation. Remember from the manifesto that Agile projects prioritize working software. That doesn’t mean that Agile projects produce no documentation. Instead, it should produce just enough documentation.
After the Agile Alliance wrote their manifesto, they created a list of agile principles.…
View On WordPress
Playing Planning Poker
In Agile you’re not estimating for individuals, you’re estimating work for the entire team. Many different developers on the team work on the same story. Some developers might decide the story is more complex. Another developer might think that the story is less complex; they could finish it up before lunch. There’s no way to tell which developer is right until the work begins.
Planning…
View On WordPress
