man confused by too complex technology

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

Black Hole No. 7: Don’t hinder collaboration with overly technical tools

C-3PO: Don’t blame me. I am an interpreter. I’m not supposed to know a power socket from a computer terminal.

We’ve already discussed how quality needs to be centrally organized by everyone in the project team. More often than not this could be made up of non-technical business users. Overly complex systems that require coding and technical expertise are at odds with this principle and could be the catalyst that causes the ‘final destruction of the Alliance!

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

In case you missed the earlier ones in the series, you can 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 organisation

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

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