This document discusses dumb software development methodologies used by incompetent managers. It identifies 12 problematic methodologies: Development by Crisis, Not Allowed To Do Development, Budget Driven Development, Axxhole Driven Development, Client Wants It Anyway, Completely Redundant Application Process, Just One More Feature Outside Schedule, Document Driven Development, Next Shiny Thing Development, Everything is High Priority, I Wish I Was Somewhere Else mode, and concludes by calling to eliminate unprofessional practices from the software industry.

1. www.auroracs.lk Software Development Methodologies of Dumb Managers Compiled by NalakaGamage Missing lessons from text books

3. Reality is often far from theory

4. Not all are professional

5. Not all are smart

6. Not all are honest

8. The Dumb & Crook Methodologies in Practice

10. Everything is a Crisis.

11. Every task, you have to “Drop everything” and work all night long!

12. Everything is a disaster.Dumb methodologies

14. Managers can be heroes in the meetings and not in development, so they like to keep on talking in meetings eating up valuable time of developers.

15. Then they will expect developers to stay late to do coding!Dumb methodologies

17. The time that a project will take is dictated by how much the client will pay, instead of how long it will take to develop the application.

18. Generally leading to massively over-budget projects and exhausted developers.Dumb methodologies

20. All wisdom, logic or process goes out the window when Mr. Axxhole is in the room, doing whatever idiotic, selfish thing he thinks is best.

21. There may be rules and processes, but Mr. Axxhole breaks them and people follow anyway.

22. In worst case Mr. Axxhole might be a completely non technical person who has positional power (i.e. Boss). Dumb methodologies

24. No matter how inane or unusable, just because the marketing teams wants it then it has to be in there.

25. Usually an over-budget, non-specified that will never be paid for.Dumb methodologies

27. You create the same application someone in your company, division, department, or cubicle has already created.

28. But you either (A) want to write your own, or (B) had no idea someone else had done it.Dumb methodologies

30. Regardless how tight the schedule, or how late the project – JOMFOS product managers can always find something strategic and groundbreaking that not only breaks the current design, but also has to be squeezed in before the unmoving release date.Dumb methodologies

32. Copious amounts of inaccurate, verbose and unnecessary documentation are prepared and maintained as if they somehow embody everything that needs to be done in the software.Dumb methodologies

34. When your development focus changes every time your boss comes back from a tech conference.Dumb methodologies

36. Management comes and tell you that something is required ASAP and next day something else is required ASAP – in the end nothing gets done!Dumb methodologies

38. When two or more of the previous methodologies are in effect the guys that really have a clue often get intoIWIWSE mode (I Wish I Was Somewhere Else) which produces some of the most unmotivated code in existenceThe Result is……………..

39. Its time to kick these unprofessional / incompetent project management practices out of software industry Let’s eliminate it ! IT industry is for smart people doing smart things in smart ways.. Let’s not dumb, crook and vicious people spoil the industry !!

40. Aurora Computer Studies The choice of the smart Aurora Computer StudiesSummerset College, 3rd Floor, DFCC Building, 135, Highlevel Road,Maharagama, Sri Lankaage www.auroracs.lk