10 Black Holes to avoid for successful application delivery. No.9

 Black Hole No. 9: Lack of cross-project visibility

Gold Leader: It’s no good, I can’t manoeuvre!

Gold Five: Stay on target.

Gold Leader: We’re too close!

Gold Five: Stay on target!

Staying on target is the ultimate goal, but don’t be too focused on the task at hand and forget the wider picture. You need complete visibility into every aspect of the project at any given time but don’t just look at this one project, managers should be able to look at staff resources across multiple projects. If team members are swamped, tasks can be re-assigned elsewhere.

A single point of reference is needed for informed decision making when sending your troops in to battle. You need complete visibility of the individual skirmishes that are going on, so that you can re-assign your forces where they are needed most. Milestones should be created to mark checkpoints and ensure that projects are running to schedule.

This is the ninth in a series of ten lessons from Yoda, on the topic of Application Quality Management.  10 Black Holes to avoid for successful Application Delivery.

Missed the others? Read them here. Black Hole No. 1: Walking before you crawl    Black Hole No.2: QA as a Silo     Black Hole No. 3: Lack of organization Black Hole No. 4: Lack of control. Black Hole No.5: Lack of visibility and out of date information. Black Hole No.6: Unnecessary re-work  Black Hole No. 7: Don’t hinder collaboration with overly technical tools  Black Hole No. 8: Not supporting all types of working practice

Share on twitter
Share on linkedin
Share on print
Share on email

We are sorry to tell you that using Internet Explorer as your browser won’t give you the best experience of this website.

To get the best value visit us via Chrome, Edge or Firefox