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…
Every process has to create value, otherwise, why are you doing it? TPS Reports are an example of a process that creates no value and/or the value it creates might be restricted to one (and not the person having to do the work surrounding the process). The tricky part of any new process is getting everyone to understand what it leads to. It’s entirely possible they might not get it because they don’t see the…
Everyone has a different style of getting something done. Whether leading people, coding, testing, strategizing or writing requirements. No one does it exactly the same way – and that’s great because then we can learn from each other. When your style collides with someone else’s, the immediate reaction will be – “I do it this way and I know my way works” – because… well… it has. But the second thought you should have is…
Here is how you build a software delivery process; What bugs you about your current system (this is whiteboarding time)? What do you want to get out of the delivery (metrics, delivering faster, more on time, a more relaxed team)? Who is involved in the delivery (either stakeholder or the roles within the process)? What things do you care about in the process (what matters to people – trust, empowerment, control, etc)? That’s it, it…
What happened? (Debug/Verbose, Info, Warning, Error, Critical) When it happened. (Dates but don’t forget timezone offsets) Why did it happen? (who did what and where) What you should do next. (is there a KB? Does this happen often) Those are the four components of any great log file, if you have those in your file the people that have to go troubleshoot will thank you kindly. The fifth component of any great log file is…