This position functions as part of an Agile team with heavy understanding and usage of the Azure DevOps tool as part of the required skillset. The System Analyst 3 is responsible for gathering, documenting, and testing clear, unambiguous business requirements from the client. Understanding the business requirements thoroughly in order to communicate business needs and system functionality to technical and non-technical stakeholders, project team members, and the user community. The System Analyst serves as the ScrumMaster (heavy usage of Azure DevOps tool) on projects and coordinates with the PMO's Project Manager for artifacts/documentation needed on State of Michigan projects.
The System Analyst is responsible for working with the project team and stakeholders to examine existing and future-state business processes, data, and systems. This information is used to guide the gathering of business requirements and executing test cases as they relate to the desired system functionality.
Responsibilities
WE THE TEKWISSEN PEOPLE
TekWissen offers you a broader portfolio of services, industry-leading solutions, and the meaningful innovations that give you greater flexibility and speed to respond to market dynamics, reduced costs and risk to improve enterprise performance, and increased productivity to enable growth.
To keep pace with global market demands, TekWissen keeps its finger on the pulse of change. Our organized approach to guiding a project from its inception to closure. Managing projects is becoming more and more important as we enter the digital era. To cope with the pace that this transition demands, a method is required to manage projects so they can yield quality work, while incorporating efficient use of time and resources.
Project involves identifying which quality standards are relevant to the project and determining how to satisfy them.
It is important to perform quality planning during the Planning Process and should be done alongside the other project planning processes because changes in the quality will likely require changes in the other planning processes, or the desired product quality may require a detailed risk analysis of an identified problem. It is important to remember that quality should be planned, designed, then built in, not added on after the fact.
Capabilities and accomplishments in one TekWissen business enhance the opportunity for success in the others. Put simply, TekWissen's unique combination of attributes promotes success.