David Wright

Articles by David Wright

Cascade #15 – Leave a record of what you have done, so the project will not miss you if you leave.

  Leave a record of what you have done, so the project will not miss you if you leave.            If change is the only...

Cascade #14 – It

  Cascade #14 - It’s the Deliverable (that matters), not the Task.The final deliverable is the Information System ready to be used effectively by...

Cascade #13 – One Architect/Analyst can generate enough work for two Developers and one Tester; structure your project teams in this ratio.

  Cascade #13 -   One Architect/Analyst can generate enough work for two Developers and one Tester; structure your project teams in this ratio.This is...

Cascade #12 – Specialize

  Specialize – each member of a team assigned to a project should  do what they do best for the length of that project. With limited...

Cascade #11 – Once a project is started, finish it.

  Once a project  is started, finish it. Even with a good process to pick the right projects to execute, there will be a strong if...

Cascade #10 – Pick the right project(s) for the business.

     Pick the right project(s) for the business. At any one time, the IT department of an average company is running multiple projects. How did...

Cascade #9 – You don’t need to invent your Architecture from scratch.

The good news is that you do not need to invent an IT Architecture method for your company. Many authors and vendors have methods available already....

Cascade #8 – Use Architecture to describe the business, before, during and after projects.

  Use Architecture  to describe the business, before, during and after projects. “Architecture” is now a widely used term associated with Information Technology. The number...

Tech News