Business Systems Analysis / SAFe Agile

As a Business Analyst with SAFe Agile experience at Peraton, your primary responsibilities will include engaging with stakeholders to collect and document requirements, assessing existing Epics, Features, and User Stories for alignment with mission objectives, and working closely with Agile scrum teams. You'll also support PI Planning sessions, brief senior leaders on Agile team statuses, and contribute to workflow documentation. Your role is essential in ensuring continuous improvement of customer products and services to meet current and future needs.

To qualify for the Business Systems Analyst position at Peraton, you need a Bachelor’s degree in a related field along with a minimum of 5 years of relevant experience. Alternatively, if you have 9 years of equivalent experience, that can substitute for the degree. Proven experience with SAFe Agile methodologies and working with federal customers is essential, while certifications such as Security+ CE or CISSP will give you an edge in the selection process.

Peraton is committed to the professional growth of its Business Analysts by providing opportunities for collaboration across Agile teams, access to continuous training in Agile methodologies, and involvement in substantial initiatives such as the Department of State Diplomatic Security Cyber Mission program. You'll be supported through mentoring, resources, and a focus on team dynamics to enhance the overall organizational performance and your personal career development.

The target salary range for the Business Analyst position at Peraton is between $86,000 and $138,000. This range is based on experience and relevant qualifications. It reflects Peraton's commitment to providing competitive compensation while recognizing the value that skilled professionals bring to the organization.

Yes, an active Secret security clearance is required for the Business Analyst position at Peraton, with the ability to obtain a final TS/SCI security clearance. This requirement is crucial for working with the Department of State and ensuring that sensitive information is handled appropriately.

When discussing your experience with SAFe Agile methodologies, focus on specific projects where you've implemented Agile principles, how you facilitated collaboration in scrum teams, and any measurable outcomes from your efforts. Highlight your role in PI Planning sessions and how you engaged with stakeholders to ensure requirements were clearly understood and documented.

In an Agile environment, prioritizing user stories involves collaborating closely with stakeholders to understand their needs and the business value of each story. Discuss your methodology for assessing complexity and impact, the importance of stakeholder feedback, and any criteria or frameworks you use, such as MoSCoW (Must-have, Should-have, Could-have, Won't-have).

To gather requirements from stakeholders effectively, I utilize a combination of techniques such as one-on-one interviews, workshops, and surveys. I ensure to ask open-ended questions to capture comprehensive insights. Being proactive in follow-ups and clarifying any ambiguities also helps build confidence and trust with stakeholders, ensuring their needs are fully understood.

To ensure that Epics and User Stories align with organizational goals, I continuously engage with leadership to understand the mission and vision, then cross-reference requirements with these objectives during backlog grooming sessions. Regular reviews and adjustments based on feedback from team members and stakeholders are vital to maintain alignment.

In an Agile project, I once faced a situation where multiple stakeholders had conflicting priorities. I approached this by facilitating a prioritization workshop, where we discussed each feature's value and developed a consensus. This helped in achieving clarity and aligning the project towards the most critical objectives, while also improving team dynamics.

I prefer tools like JIRA for documenting user stories due to its integrated features that promote transparency and collaboration among Agile teams. It allows for easy tracking of progress and facilitates communication through comments and updates. Moreover, its customization options align well with our project's specific needs.

When project scope changes arise post-development initiation, I follow a change management process that involves assessing the impact of the change on the current project timeline and resources. I communicate with both stakeholders and the Agile team to analyze the necessity and feasibility of the change before finalizing any decisions.

Communication is the backbone of a successful Agile team. It fosters collaboration, ensures everyone is aligned with project goals, and allows for immediate feedback loops. Regular stand-ups, retrospectives, and check-ins facilitate a culture of openness and trust, essential for addressing challenges quickly and iterating appropriately.

I once developed a performance metric that measured the cycle time of completing user stories from inception to delivery. This metric was significant as it provided insights into process efficiencies and helped identify bottlenecks in our Agile workflow, allowing the team to implement targeted improvements.

Creating feedback mechanisms is integral to improving products and services. I approach this by designing surveys and conducting focus group discussions to gather qualitative insights. Additionally, I ensure that user feedback is systematically documented and prioritized in our backlog for iterative improvements, fostering a more customer-centric product development approach.