1 / 11

Tips and Tricks for Recovering a Rogue IT Project

Tips and Tricks for Recovering a Rogue IT Project. Robert Bogue MS MVP, MCSE, MCSA: Security, Etc. Thor Projects, LLC Rob.Bogue@ThorProjects.com. Defining Rogue. Dictionary Definition (courtesy of Dictionary.com) Large, destructive, and anomalous or unpredictable In IT

karina-webster
Download Presentation

Tips and Tricks for Recovering a Rogue IT Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tips and Tricks for Recovering a Rogue IT Project Robert Bogue MS MVP, MCSE, MCSA: Security, Etc.Thor Projects, LLC Rob.Bogue@ThorProjects.com

  2. Defining Rogue • Dictionary Definition (courtesy of Dictionary.com) • Large, destructive, and anomalous or unpredictable • In IT • A project that was never approved but has created a life of it’s own • A project with a runaway schedule and cost that shows no signs of stopping

  3. Agreeing It’s a Rogue Project • The first step is admitting you have a problem • Agreement has to come from the bottom up and the top down

  4. Triage • Where is the project compared to a standard model? • What are the most pressing issues? • What resources do you need to resolve the most pressing issues? • Should you let this project die?

  5. Charting a Course • Integrity – Do what’s right for the organization first, the project second, and politics last. • Take the blame – even when it’s not yours. There will be time enough for post-mortems. • Create Some Slack – You can’t break the tension without breaking the tension

  6. Get Everyone on the same page • You can’t hit a moving target • You’ll never reach the end of the project if the end of the project moves as fast as you do. • If the rules keep changing, put a stop to that immediately.

  7. Back to the Basics • Do work (code) reviews – they work • Create Milestones • Eliminate Risks • Open and Honest Communication

  8. Project Management Techniques • Develop a project plan • Identify Incomplete tasks and dependencies (to ~40 hours or less per task) • Develop a risk management plan • Identify risks to the project such as cancellation, loss of key staff, etc. • Establish change management

  9. Avoiding the “Blame Game” • There’s more than enough to go around • Why didn’t you notice the project was out of control before it went rogue? • What controls do you have in place to prevent projects from going rogue?

  10. Searching for Root Causes • When did we first know it was broken? • How did we know it was broken? • Why didn’t we fix it?

  11. Questions? Robert L. Bogue(317) 844-5310Rob.Bogue@ThorProjects.com

More Related