SOFT's client located in New York, NY ( Hybrid ) is looking for a Product Analyst - Agile for a long term contract assignment.
As part of this engagement, we are seeking a team to accomplish the following goals/acceptance criteria:
1. Create a documentation / communication strategy for the Agile Release Train (ART). This should be inclusive of various document types, including requirements, designs, roadmaps, support, etc..
a. Requested Deliverables:
i. Documentation strategy document approved by ART leadership
ii. Taxonomy/classification scheme
iii. Storage location decision matrix (what goes in SharePoint vs JIRA vs Confluence)
iv. Communication plan template for different stakeholder groups
v. Style guide for consistency across the ART
2. Create the version management processes necessary to manage these documentation types.
a. Requested Deliverables:
i. Version control procedures document with examples
ii. Archival policy (when to archive vs. delete)
iii. Document retention schedule aligned with compliance requirements
iv. Branching strategy for documentation aligned with code/release branches
v. Rollback procedures for documentation updates
3. Assess current state of documentation and create a gap analysis against proposed structure.
a. Requested Deliverables:
i. Conduct initial assessment (Week 1-2) of current Confluence state and existing SharePoint/JIRA content
ii. Create prioritization matrix for documentation needs across all 19 applications
iii. Deliver gap analysis report identifying critical missing documentation that poses key migration risk
iv. Map existing documentation to new structure and identify orphaned/duplicate content
4. Create guidance to teams on Confluence cleanup efforts.
a. If Confluence will be retained, a standard structure needs to be outlined and process for document lifecycle should be created (i.e., once a feature goes from inception to production, what should each team do with the transitory confluence pages?)
b. Requested Deliverables:
i. Migration playbook (step-by-step guide for teams)
ii. Before/after structure comparison
iii. Confluence page tagging/labeling standards
iv. Estimated timeline for cleanup per team
v. Success metrics (e.g., 100% of active pages following new structure)
5. Create standardized requirements documentation templates, including the following aspects:
a. Requested Deliverables:
i. Standardized requirements documentation templates with the following
1. Data flows and sequence diagrams
2. File specifications and data dictionaries
3. API contracts (if applicable)
4. Error handling and exception scenarios
5. SLA/performance requirements
ii. Train the key resources that will be maintaining the proposed documentation.
6. Using the template defined above create process flow and requirements documentation for a prioritized list of applications. Prioritization will be based on those applications that are being replaced, as opposed to lift and shift.
a. For instance, a Datawarehouse application called Compass is being migrated from an on prem to a cloud disposition. It has at least 10 interfaces with partner systems that need to be migrated, however design and file spec documentation for many of these is missing. Since, the interfaces are being replaced, documenting these is a key pre-requisite for the shared service architecture team s design.
b. Requested Deliverables:
i. For the top three - five applications, as defined by the Product Owner, document the process flow and detailed requirements for the current production versions.
Key Responsibilities:
1. Top five hard skills:
I. Requirements Elicitation & Documentation
a. Technical documentation skills (PRDs, user flows, process maps)
b. Experience with wireframing/prototyping tools
c. Experience with process mapping tools (Visio, Lucidchart, Miro)
d. Knowledge of BPMN, swimlane diagrams, value stream mapping
e. Ability to effectively extract/create in SharePoint, Confluence, JIRA, JIRA Align
II. Data Analysis
a. Ability to write queries, extract insights, and validate product assumptions with data
b. Excel/Spreadsheet Mastery
1. Advanced functions (VLOOKUP, pivot tables, macros)
III. User Story Writing & Backlog Management
a. Experience crafting clear acceptance criteria and definition of done
b. Proficiency with tools like JIRA, JIRA Align, or similar agile platforms
IV. Agile/Scrum Methodology
a. Demonstrated experience running ceremonies (sprint planning, refinement, retrospectives)
b. Understanding of scaled agile frameworks (e.g., SAFe)
V. API & Integration Understanding
a. Basic knowledge of REST APIs, webhooks, data flows
2. Top five soft skills:
I. Stakeholder Management
a. Can balance competing priorities from engineering, business, and customers
b. Skilled at managing up and influencing without authority
II. Communication & Translation
a. Bridges technical and non-technical audiences effectively
b. Can simplify complex concepts for diverse stakeholders
III. Critical Thinking & Problem Solving
a. Asks `why` to get to root causes vs. jumping to solutions
b. Can evaluate trade-offs and make data-informed decisions
IV. Adaptability & Autonomy
a. Can hit the ground running with minimal onboarding (critical for contractors)
b. Comfortable with ambiguity and changing priorities
V. Collaboration & Facilitation
a. Works effectively within cross-functional teams
b. Can facilitate productive discussions and drive consensus
Please refer to the Position ID when inquiring about a job posting or sending in your resume.
***INDEPENDENT CONSULTANTS ONLY! NO THIRD PARTIES/NO SUB CONTRACTORS***
Never miss an opportunity! Create an alert based on the job you applied for.
