Do you trust your team? If you do, anything is possible. If you don’t, nothing will ever happen. If you never try, you will never know.
We all have our own Systems that we use to do things. I.e., how we structure our files, create new projects, do error handling, log errors, etc. It generally gets the response of – “that’s just how I do it”. When you’re running Solo, the System of One works great because the only evaluating party is yourself is you. You get to decide whether it’s worth it or not, how it helps you, and what…
The goal of any new process is to solve a problem. If you are not able to solve a problem with your process then you have introduced a new problem to your team, one they probably didn’t need. Make sure you know the goals, before you build something new (that might not even need to exist).
Software that is stable. Software that delivers on the features that you downloaded it for. Software that is simple and intuitive to use. Do the core features work from release to release? Those are the basics of any software solution that from release to release should always be there. Everything else is an add-on bonus, but the core, the core should never be buggy.
Multiple Teams can have multiple processes and systems for what they do. This isn’t a bad thing – build the process, methodology or system that fits the team for what they are doing. The Agile methodology for software is built around tenets to accomplish goals and not implementation details itself. If you are working with multiple teams with multiple ways of doing things and each team is performing well the question should be are you…