As a Test Manager at Olenick & Associates, I am a big believer in the idea that the more planning at the beginning of the project means the rest of the project will go a lot smoother and faster. In this blog post series I am reflecting on various processes and how lack of process, or processes not being followed, can really screw up a project.
As a Test Manager at Olenick & Associates, I’ve worked on many projects, both big and small. There have been projects where processes were followed and projects where there was not much in the way of processes, or processes were not followed. I am a big believer in the idea that more planning at the beginning of the project means the rest of the project will go a lot smoother and faster. In this blog post series I look to enlighten you on the importance of Project Management and how the process is critical to successful testing and project outcomes.
Requirements are the baseline for any project, as without requirements we don’t have a definitive list of set functions that the business requires the system/software to do.
No matter how well something is planned, there will always be something that comes up that was not planned for.
It is just as critical that processes are in place for a project, as it is for those processes to be flexible enough to allow for things to happen and adjust in a way that is productive to the project.
When you have multiple developers working on a project, bugs can be hard to pin down. When was the bug introduced? Whose code was it? Did our merge introduce issues? Tracking down these kind of questions gets increasingly complicated – and costly – as you add more collaborators.
The United States electric grid is a network of transmission and distribution lines, substations, transformers, and devices that deliver alternating current electricity from power generation sources (coal, nuclear, hydroelectric, wind, solar, biomass, and natural gas generation plants) to homes and businesses. Development of the infrastructure and power grid was one of the great electrical engineering achievements of the 20th century. However, increasing power demands and increasing system complexity require major improvements to meet the requirements of the 21st century. Electrical power consumption in the United States has increased from 330M kWh in 1950 to over 4100M kWh in 2014.
It is an exciting time for Energy Delivery Systems. Industry investment in smart grid and Advanced Metering Infrastructure (AMI) are fueling advances in systems that store, process and manage data. Security protection standards (most notably those of the North American Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) program) are changing the way Supervisory Control and Data Acquisition (SCADA) systems are integrated and supported. In addition, growing feature sets for Outage/Distribution Management and Mobile Workforce systems are enhancing the usefulness of these tools.
Success in this climate requires more from today’s IT project and support teams. Increased regulation requires stringent process definition and more exacting system configuration. Systems are becoming increasingly sensitive to changes introduced through interfaces and data maintenance changes. Simply put, there is less room for error. Couple these factors with the integration challenges of third party provided systems and it’s enough to make one’s head spin!
As mobile testing becomes more prevalent, new questions and problems arise as compared to usual testing on a computer. While computer applications generate crash logs, and most likely send these logs back to the developer’s server automatically, it is harder for a mobile device to do the same. In this case, it requires mobile testers to be able to track, identify, and save the log files during testing in order to communicate and collaborate with mobile developers.