Business Analyst/Scrum Master

As a Business Analyst/Scrum Master at iCallidus, you will be responsible for analyzing propositions and assessing decision-making factors such as strategic alignment and risk. You will collaborate closely with Product Owners and Managers, define product approaches, develop roadmaps, and manage project risks. This role also involves writing user stories, managing internal documentation, and creating clear pathways for delivery, all designed to meet user needs effectively.

To qualify for the Business Analyst/Scrum Master role at iCallidus, you should have at least three years of Scrum Master experience in a medium to large Agile enterprise. Certification as a Scrum Master is preferred. Additionally, candidates should possess in-depth knowledge of digital and web services, strong requirements gathering skills, and familiarity with IIBA best practices. An active MBI clearance is also mandatory.

iCallidus offers a competitive benefits package for the Business Analyst/Scrum Master position, which includes medical, vision, and dental coverage, a 401(K) plan, short-term disability, and basic life insurance. After the initial 90-day probationary period, paid time off (PTO) will be available, ensuring work-life balance and employee well-being.

The Business Analyst/Scrum Master at iCallidus contributes to project success by performing thorough analyses, mapping out risks, and defining measurable success criteria. By collaborating with various stakeholders and employing agile methodologies, you ensure that user-centric designs are prioritized while maintaining clear documentation and regular updates. Your insights will help drive projects that achieve high-quality results and enhance organizational performance.

Yes, an active MBI clearance is mandatory for the Business Analyst/Scrum Master position at iCallidus. This requirement reflects our commitment to security and readiness to operate within sensitive environments. Additionally, candidates must be U.S. citizens or lawful permanent residents.

When prioritizing user stories, I assess each story's impact on the overall project goals and the end-user experience. I utilize the MoSCoW method or other frameworks to categorize stories as Must-have, Should-have, Could-have, and Won't-have, ensuring that the most valuable features are developed first based on user feedback and stakeholder input.

Sure! In a previous project at my last job, I identified a potential resource shortage that could delay our timeline. I organized a meeting with stakeholders to discuss the risk and we developed a plan to reallocate resources and brought in external contractors. This proactive approach allowed us to maintain our timeline while effectively managing the risk.

For effective requirements gathering, I employ techniques like interviews, workshops, and surveys with stakeholders. I also create user personas and journey maps that help visualize user needs and ensure all requirements are clearly understood and documented in user stories, facilitating alignment across the team.

When conflicts arise, I first foster an environment of open communication where team members can discuss their perspectives. I facilitate a conversation that encourages active listening and seeks common ground. By focusing on the project's goals and outcomes, we can collaboratively find solutions that benefit the team's cohesion and project success.

My process for developing a product roadmap starts with gathering input from stakeholders and analyzing the project's vision and goals. I prioritize objectives based on user feedback and align them with strategic targets. After drafting the roadmap, I review it regularly and adjust it based on evolving needs or challenges encountered during implementation.

I rely heavily on tools like Jira and Trello for backlog management, sprint planning, and workflow tracking. These tools enhance collaboration amongst team members, enabling us to visualize progress easily. I also utilize Confluence for documentation, ensuring all relevant information is accessible and organized.

A successful project deployment is defined by the deliverables meeting user requirements and stakeholder expectations. This includes achieving the predefined success criteria within the timeline and budget, ensuring a smooth transition for the users, and receiving positive feedback on the project's overall impact on their experience or efficiency.

My experience with stakeholder communication is grounded in regular updates and a focus on transparency. I use status reports and meetings to keep stakeholders informed about project progress, risks, and changes. Additionally, I encourage feedback, ensuring their needs and concerns are addressed throughout the project lifecycle.

I measure the success of a Scrum team by evaluating key metrics such as velocity, sprint completion rates, and stakeholder satisfaction. Regular retrospectives allow the team to reflect on areas of improvement and successes. Ultimately, a successful team is one that consistently meets its goals and contributes to a positive team culture.

Absolutely! The INVEST criteria stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. Each user story should meet these criteria to ensure they are effective and manageable. This helps the team break down stories into workable segments, facilitating efficient development and providing clear value to the end-users.