IT Project Sanity Checklist



From my perspective as a software developer, a tool you could use to avoid some pitfalls when starting a new IT project. Sum up the points below. Higher score is better.

"Keep it Simple"

[#1] The lines of code would ...

[#2] The amount of version numbers to keep updated would ...

[#3] The proposed technology ...

[#4] Onboarding a new software developer will become ...

"Not Invented Here"

[#5] The project is about ...

[#6] The technology is developed by ...

[#7] The users of this technology ...

[#8] We can not use that existing solution because ...

"Agility"

[#9] The project delivers value ...

[#10] Should the project has to be shut down halfway in ...

[#11] The size of the project is ...

[#12] The product release process will become ...

"Business Value"

[#13] When you describe the project to a colleague from another department ...

[#14] The pay back time of the project based on time required and your salary ...

[#15] If you play pretend that the company is at the brink of bankruptcy ...

[#16] When this feature is released the existing customers will ...

[#17] Our sales department says the project ...

"People"

[#18] After completion of the project the employees ...

[#19] The people involved in the project ...

[#20] The team tasked with the project ...