EVERYTHING IS A PROJECT

I am coming back to this idea over and over again for the last 15-20 years. When we discuss developing software, there is a universal consensus that it is a project. A project that is unlikely to succeed unless treated as one, starting with a vision and then progressing to requirements/user stories, architecture/design, development/testing, deployment/maintenance, and continuous improvements/enhancements/refactoring throughout the system’s lifespan.

Very few people would jump to the implementation of sizable software to be used by many people just based on a general idea of how it might work (except for prototyping during the R&D phase). And those who do rarely get a good return on their investments (except for a few brilliant minds who are just destined to succeed via their brilliance and strike of luck).

However, when it comes to defining the development process, business process, organizational structure, requirements management flow, system modernization approach, or project management strategy, it is often okay just to give it a shot. Even though it might have a huge impact on the productivity of the entire organization. Often, the general direction is just to reverse what was done before. For example, if waterfall did not work well, let’s switch to textbook agile and see how it fares; if moving complete control to offshore and consulting companies was unsuccessful, let’s bring everything back in-house. Most of the time, quick timelines are given for executing a change, which does not allow enough time for due diligence.

My experience has led me to the conclusion that SDLC (Software Development Life Cycle) best practices can, and probably should, ?be adjusted and applied to process development for most organizations, as well as to various projects and personal aspirations such as home remodeling, landscaping, crafts, self-publishing, or sports. Thinking about it, it might also apply to political processes and regulations. I also noticed that subconsciously, I apply those principles in my daily life.

Below is a flowchart I put together about eight years ago, showing how iterative? SDLC methodology could be applied to process development.

This is not a one-size-fits-all approach. In different situations, various steps and levels of formalities may be required. Still, the core principle remains the same: everything is a project, and it works better when treated as such.

I would love to hear your comments and thoughts on this.

And if you really like it, you can ?https://www.buymeacoffee.com/itealistic