Tag Archives: Oil and Gas

Defect Management in an Agile Environment


The purpose of defect management is to identify bugs or defects of the software and provide information to improve the development process.

In Agile, the process of detecting defects works in parallel to the software development process, and once mastered, can prevent a lot of potential problems.

Scrum per se as a framework does not explicitly show you how to handle defects. With scrum you can bring more accountability to the entire project, however  one lacks clarity on how the teams should operate in the process of delivering the software. Some questions that arise are..

…When a bug is found does it become part of the sprint backlog

…What if adding it to the sprint skews the burn-down and makes it harder to meet the sprint goals?

…What by adding defects to the product backlog delays an important fix?


 Defect in Traditional Environment

Conventional Waterfall development consists of a system that can be included in the definition of ‘Done’ when it is analyzed, designed, and coded. Development needs to pass the quality testing phase. Bugs and issues detected during this stage are called defects. They are researched and re-tested by the developers before sending for finalization.

However, this method lacks the ability to preven

t the bugs. Developers are required to break down software code and check results. Once completed, they move on to another project and defects in the previous one causes unnecessary delays in the workflows. This adds stress and instability resulting in an impeded development process.


Problem Management in Agile Environment

Whenever an error occurs in the user story of a current or past sprint, it should be immediately identified and resolved to maintain  quality. The methodology may vary from one scenario to another. And so here we elucidate few scenarios:


Scenario 1: When a Defect is Detected During Acceptance Testing of a User Story:

In most of cases, it is better to detect and fix a problem as soon as it is discovered in the QA testing. When this isn’t possible, the user story should go back to the developer for resolving the defect. It is re-tested several times until the complete resolution of a defect. In this scenario, recording of a defect can also help. The teams stay abreast of the waste that takes place between the phase of development and testing. And metrics can be used for a better problem management.


Scenario 2: When the Team Conducts Regression Testing on the Functionality of Software:

Sometimes, developers may conduct a regression testing on the user stories that are already accepted by the product owner. In this story, there can be a defect that needs to be properly tracked and unraveled.

It is always a possibility to create a defect for such issues. However, you should resolve it immediately instead of creating a defect to be tracked.


Scenario 3: A Story is Noted as Done Despite Some Known Defects that are Deferred:

In a deferred defect, there lies a sub-feature of a user story that needs full implementation. Here, it is important to create a new story to fix the defect. These may include defects having requirement specifications. In Agile environments, such defects are sized and prioritized according to other factors.


Scenario 4: A Defect Found in the Demonstration of a User Story:

In every 2-3 weeks, developers demonstrate user stories to the stakeholders. If something is found to be broken during this demonstration, a defect is created, prioritized, tracked, and resolved for it. However, the issues in the unaccepted stories can’t be marked as Defects. In this scenario, the story isn’t complete and defect can’t be created.

As a matter of fact, follow a well-defined problem management practice to resolve the defects in the software.

In the end, the best way to manage problems is to prevent them from happening.


Houston Oil and Gas: Top 4 ERP Solutions to Tap the Energy Revolution

An up-and-coming oil and gas behemoth, Texas is a key component of U.S. energy security. It leads three-tenths of our crude oil-refining capacity — and a third of all oil production.

A report by the U.S. Energy Information Administration (EIA) states a new-found resilience in the shale sector. This will create a significant surge in oil and gas production over the next few years.

Shale producers from the Eagle Ford Shale and Permian Basin are using technological advances and safe hydraulic fracturing – also known as ‘fracking’ to tap vast oil and natural gas reserves that were previously locked away in tight-rock or shale formations.

Extracting these new resources will continue to inject billions of dollars into local economies and will be the biggest single reason for a spur in the energy revolution.

This trend, in turn, will create a compelling need to implement long-term IT development solutions for mid-stream and downstream companies who are looking to find more significant control over processes and efficiencies across existing functions.


ERP Solutions in the Oil and Gas Industry

oil and gas houston erp


Enterprise resource planning (ERP) is an integrated way of weaving core business processes together, often by an intermix of software and technology, in real-time.

An ERP system can play a crucial role in automating, standardizing and digitizing processes in a volatile ecosystem such as oil and gas, where a systemic and cross-functional approach can offer a bird’s eye view of operations that impacts profitability. Further, it can facilitate error-free transactions and production, thereby enhancing an organization’s efficiency.

Houston-based energy companies looking to connect people, digital process and data can cut down under-performance, costs and wasted time by leveraging integrated ERP solutions that will allow them to move into the world market quickly.

Let’s look at the potential benefits of implementing such a system –


#1 Replace Customized Legacy System with a Future-Ready Platform

An easy to use, intuitive ERP integrated platform supports a company’s contract terms and business growth targets, manage resources, plan for what’s ahead, including risks and support multiple operations.

It cross-connect assets across other vendor supported gathering and management platforms to leverage synergies for itself and its customers.


#2 Optimize Business Workflows

Oil and gas companies need people, resources, and utilities to manage critical assets in their operations. Scheduling demands and short turnaround times need stringent processes and capabilities.

Through the three pillars of standardization, automation, and new technology they can eliminate costly customization that were inhibiting margin, growth and potential future revenues.

An ERP system helps gather valuable data in real-time to ensure resources allocated are optimally used with deadlines. Also, it can avert any potential crisis that may arise.


#3 Reduce Capital Cost, Complexity and Risk

A right ERP provides full visibility of a company’s financial position especially in areas such as AFE’s (Authorization for Expenditure) and Procure to Pay with specific governance needs. Further, there are modules for Purchasing, AP, AR, Invoice Workflow, Fixed Assets and Integration with Quick Books that give control of complete CAPEX spend.

Companies can use ERP software to identify project risks well in advance and accelerate risk response with integrated risk reporting and remediation.


# 4 Business Analytics Integration

An ERP system can embed analytic tools with internal applications to monitor performance. With technology, companies can predict trends and identify new opportunities based on master data integration and other data conversion activities.

In a complex, ever-changing market such as the energy sector, an ERP system aligns to the nth degree to your proven business processes. Our consultants at Terra ATS have over 40 years of combined experience helping businesses put in place customized ERP solutions to your specific needs.

Schedule a call with us today to help us build the perfect oil and gas ERP system for your company.