Sr. Software Engineer / Manassas, VA Job
Job Description Job Attributes+
Rotary and Mission Systems
XEBT3A:C4USS Software Eng
Manassas, VA 20110, US
TEMPO: 9X80A - Standard Fri to Fri (Flex & Rigid)
We are seeking experienced software engineers to shape the development of our software as Product Owners. The Product Owner (PO) is a member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components for the team. The PO has a significant role in quality control and is the only team member empowered to accept stories as done. This role has significant relationships and responsibilities outside the local team, including working with the Chief Engineer (who is responsible for the Program Backlog) and preparing for the Program Cycle Planning events.
Before planning events, the PO updates the team backlog and reviews the cycle goals/objectives. During the event, the PO is involved with story definition, providing the clarifications necessary to assist the team with their story estimates and sequencing. The PO also drafts the team’s specific objectives for the upcoming cycle.
o Maintaining the team backlog – With input from Chief Engineer and other stakeholders, the PO has the primary responsibility for building, editing, and maintaining the team backlog. Consisting mostly of user stories, it also includes defects and enablers. Backlog items are prioritized based on user value, time, and other team dependencies determined in the cycle planning meeting and refined during the cycle.
o Sprint Planning – The PO reviews and reprioritizes the backlog as part of the prep work for Sprint Planning, including coordination of dependencies with other POs. During the sprint planning meeting, the PO is the primary source for story detail and priorities and has the responsibility of accepting the final sprint plan.
o Just-in-time story elaboration – Most backlog items are elaborated into user stories for implementation. This may happen before the sprint, during sprint planning, or during the sprint. While any team member can write stories and acceptance criteria, the PO has the primary responsibility for maintaining the flow. The goal for the PO is to two sprints’ worth of stories ready in the team backlog at all times (more would create a queue, while less might inhibit flow).
o Supporting Acceptance Test Definition – POs participate in the development of story acceptance criteria, draft them when feasible, and provide examples when needed.
o Accepting stories – The PO is the only team member who can accept stories as done. This includes validation that the story meets acceptance criteria and has the appropriate, persistent acceptance tests, and that it otherwise complies with its Definition of Done (DoD).
o Understand enabler work – While POs are not expected to drive technological decisions, they are supposed to understand the scope of the upcoming enabler work and to collaborate with RA & SYS teams to assist with decision-making and sequencing of the work.
o Participate in team demo and retrospective – As the person responsible for requirements, POs
•Creating testing tools for development and integration
•Creating medium to large scaled systems using distributed components / micro services
•Ability to troubleshoot in a multi-threaded, multi-core and usually real-time or near real-time environment
•Java Programming Language
•Agile Processes / DevOps
•C/C++ Programming Language
•MATLAB Programming Language
Who We Are
<div style="text-align: justify;">At Lockheed Martin, veterans are at the center of everything we do — in fact, one in five of our employees has served in uniform. We are proud to help men and women like you successfully transition into civilian careers. Join us and you will find opportunities to take on the same kind of long-term challenging assignments you tackled while in the military.</div>