When I started as a software tester, I considered the software development process other people responsibility. This post explains why I was wrong with that attitude. This post is based on a remarkable book written by Chad Fowler, The Passionate Programmer.
That attitude broke on my back. In our process, I was given the role (and I accepted it) as project quality gatekeeper. I expected a how-to process document that is a Unicorn. Nobody wrote that document. They just used process fancy words like agile, burndown charts, user stories. Which all led to my quality gatekeeper role. You first need to understand what is offered in the world of the software development process to avoid being in my shoes.
To get to know what is offered in the world of software development processes, I highly recommend the book from Johanna Rothman: Manage It! Your Guide To Modern, Pragmatic Project Management.
Here is what you will learn from this book:
- How to start, plan and schedule a project
- What is Project Life Cycle
- Work Estimation and Schedule Games
- Project Team
- Project Steering and Rythm
- Metings (you will never again fall asleep at a meeting)
- Testing Integration into Project
- Project Dashboard
- And most importantly, how to finish a project.
That book was a revelation for me. And now, I can contribute to the project software development process. Remember that every software development project is unique!