NVP Software Solutions

Tag: PM

  • So you want to be a Software Test Manager?

    [et_pb_section fb_built=”1″ admin_label=”Section” _builder_version=”3.22″][et_pb_row admin_label=”Row” _builder_version=”3.25″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” custom_padding__hover=”|||”][et_pb_text admin_label=”Blog Post Content” _builder_version=”3.0.87″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” use_border_color=”off” border_color=”#ffffff” border_style=”solid”]

    So you want to be a software test manager and are wondering about your decision?

    There are plenty of ways to become a software test manager. If you ask current test managers how they got there, these are some of the answers you may get:

    • Traditional: They started as a tester; became a test lead and ultimately a manager.
    • They were a lead in some other area and a managerial role opened up which they took.
    • They have no background at all in any sort of role but were seconded to a Test Manger Role.
    • It is part of the career path (particularly applicable to larger organisations).

    Regardless of which path you used to get to Software Test Manager there are several common aspects once you are there:

    • Metrics are crucial at both the department and project level.
    • Much of the management is similar to other management roles.
    • Be prepared to communicate a lot and to explain over and over again why things are being done in a particular way.

    There is a lot of conferences, user groups or LinkedIn groups that cater to Test Management. One of the better known ones is the QUEST Test Manager’s Workshop.

    Due to ongoing evolution, it is critical not to lose your technical edge even as a manager. If you find yourself looking for a job later, it is helpful to be current with at least some aspects of technology. While it may not be an immediate concern it will certainly help..

    Some companies will provide career paths for personal and technical development and improvement.

    Make sure to join LinkedIn Groups and your local Quality Assurance group. These are great options for networking and finding out other information. Take a look also at straight management groups whether related to testing or not. They have lots of information for you.

    [/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]

  • Early vs Late Testing

    Early versus Late Testing within a project is an ongoing debate within the software testing industry. With the Waterfall methodology, active testing was not possible until late in the development cycle when the project was ‘thrown over the wall’ to testing and the testers started what some called the ‘final exam’. A long test-fix cycle often ensued. Many newer methodologies promote earlier involvement and many of the recent ones promote continuous testing of multiple builds using test automation. With a broad definition of testing that encompasses more than just direct Validation it is quite possible to start some form of testing very early in the project. However, some feel that we have obtained as many benefits as we possibly can from early testing and we need to bring back an emphasis on late cycle testing when the system is fully developed in order to prove everything works together.

    This debate is missing the point of the testing process. The only question is when is it appropriate to do testing and this can be answered at the time of planning and with the help of Quality Assurance. Testing has to be completed when it is appropriate and when the necessary items are in place to support that endeavor. During the test planning process, it is necessary to identify what testing needs to be completed. Once we know what has to be completed, then we can identify where in the process it can be completed. Quality Assurance processes allow that identification to take place easily. With some overarching process in place that indicate what the organisation requires in the way of Risk reduction, it is easy to identify what testing is required and then map that to the appropriate place in the Software Development Life Cycle.

    While Early or Late testing may not always be appropriate, early planning is always necessary and Quality Assurance guides that planning.