Meeleetester

So where to shift now that testers are part of reviewing the business cases, participate in creation of user stories and backlog grooming, have the ability to use monitoring in different environments, and everything in between, meaning participate in different parts of the software development and delivery life cycle? Well, I think that we could benefit a lot from trying to look at where we generate mistakes. If we sum up the development life cycle, regardless of how often you release, or whether you follow a  waterfall, agile, or devops approach, it all starts with some ideas, business cases, requirements on a higher level, before going into the process of refining the requirements, developing, testing and releasing the changes to the end-users. We previously shifted left and right trying to mitigate and correct issues that occur along the way in the process, without looking into where these mistakes originated. All of the ideas or requirements start in someones mind, with all the

2010 - a full year in, "if testers are not involved early, we do not want to be involved later" After being employed full-time for a year or so, we finally completed a full circle of releases, both the major releases involving a full scaled up beta/pilot program, and some minor releases, as this was taking place on a yearly basis. After each ended project, a small group of people from different teams formed a retrospective team, to go over what was done good and what could be done better next time, for all projects individually but also as a whole. This was before any agile methodologies were introduced. During the retrospective, or post-mortem analysis I think it was called at the time, we from the test team argued that we were not involved early enough and that we ended testing specifications that were well out of date due to our late involvement. This was taken into consideration and that from next phase we were to be included in all start up meetings, and walkthroughs