Oasis Systems is actively seeking a Systems Engineer to support Air Force Distributed Common Ground System Program (AF DCGS) at Hanscom AFB, MA.
Bachelor of Science Degree in Computer Science or Engineering related field from an accredited university and 3-5 years Systems Engineering and/or software development experience – required
Scaled Agile Framework experience and SAFe certification in leading SAFe and (PM/PO) - desired
Experience executing on Agile Scrum programs
Must have an active US security clearance
Develop and communicate the program vision and roadmap - Product Management continuously develops and communicates the vision to the development teams and defines the features of the system. In collaboration with System and Solution Architect/Engineering, they also define and maintain the Nonfunctional Requirements (NFRs) to help ensure that the solution meets relevant standards and other system quality requirements. They are responsible for the roadmap, which illustrates, at a high level, how features are intended to be implemented over time.
Manage and prioritize the flow of work - Product Management manages the flow of work through the program and into the program backlog. Product Management is responsible for making sure that there are enough features ready in the backlog at all times. For example, they have feature acceptance criteria that can be used to establish that it meets its Definition of Done (DoD).
Participate in PI planning - During each PI planning session, Product Management presents the vision, which highlights the proposed features of the solution, along with any relevant upcoming Milestones. They also typically participate as Business Owners for the train, with the responsibility of approving PI Objectives and establishing business value.
Define releases and program increments - Owning the 'what' means that Product Management is largely responsible for release definition as well, including new features, architecture, and allocations for technical debt. This is accomplished through a series of Program Increments and releases, whose definition and business objectives are also determined by Product Management. Product Management works with release management, where applicable, to decide when enough value has been accrued to warrant a release to the customer.
Work with System Architect/Engineering to understand Enabler work. While Product Management is not expected to drive technological decisions, they are expected to understand the scope of the upcoming enabler work and to work with System and Solution Architect/Engineering to assist with decision-making and sequencing of the technological infrastructures that will host the new business functionality. This is typically done by establishing a capacity allocation, as described in the Program and Solution Backlogs article.
Participate in demos and Inspect and Adapt (I&A) - Product Management is an active participant in biweekly System Demos, including the aggregate one at the end of the PI. They are also involved in the assessment of Metrics, including evaluation of business value achieved versus plan, and are active participants in the inspect and adapt workshop.
Build an effective Product Management/Product Owner team - Though the Product Owner and Product Management roles may report to different organizations, forming an effective extended Product Management/Product Owner team is the key to efficient and effective development. Such a team also contributes materially to the job satisfaction that comes with being part of a high-performing team, one that routinely delivers on its quality and vision commitments.