About the job

What we are looking for 

• Clearly defined terms: Good that you have provided clear definitions of terms like "Issue," "Story," "Bug," "Task," etc. This will help with better understanding and consistency in communication.
• Scrum Statuses: The suggested statuses seem appropriate and align with the scrum methodology.
• New Issue Flow: The proposed flow for managing new stories in Jira seems well thought out and systematic.
• Avoiding old statuses: Good call on eliminating the "Old Issue in Platform" status, it can lead to confusion and miscommunication.
• Responsibility assignment: The suggestion of assigning responsibility to the original developer for bugs is a good one. This can help to avoid any confusion and speed up the resolution process.
• Adding labels: Adding labels is a good way to add additional metadata to an issue. This can be useful for categorizing and filtering.
• Technical Debt: Emphasizing the importance of tracking technical debt as soon as it is recognized is important, to ensure it doesn't get forgotten.
• Shortened statuses: Shortening the statuses to save screen real estate is a good call, making it easier to manage the issues.
• Review by multiple teams: Involving multiple teams in the review process, like Development, QA, and DB teams, will ensure better quality and collaboration.
• Full and glorious detail: Encouraging product managers to provide full detail in creating issues in Jira will help with a better understanding of the issue and its resolution.

Preferred Skills 

• At least 1 to 2 years of experience in Project management and implementation
• Prior Project Manager experience with Agile Delivery Framework (preferable)
• Ability to think strategically and understand how solution approach fits into technical environment
• Demonstrated Project management skills
• Strong analytical skills with the ability to clearly articulate complexities
• Extensive experience of driving results and collaborating in a cross-functional and global environment
• Good communication, collaboration, presentation and influencing skills
• Ability to identify opportunities to reduce costs and / or timelines without adding unacceptable risks to quality
• Flexibility in supporting various time zones, as this role supports a global initiative
• Independent thinker and comfortable with making project level decisions
• Creates and maintains the User Stories Backlog.
• Connect with System Architect/ Engineering team/Other PO’s and Product Manager to develop and groom the team backlog
• Prioritizes and sequences the user stories backlog according to business value or ROI
• Assists with the elaboration of features into user stories including the acceptance Criteria that are granular enough to be achieved in a single sprint.
• Conveys the Vision and Goals at the beginning of every PI and Sprint to the scrum team
• Participates in the daily Scrums, Sprint Planning Meetings and Sprint Reviews and Retrospectives.
• Inspects the product progress at the end of every Sprint and has complete authority to accept or reject work done.
• Communicates status externally on regular basis and work with other PO’s and SMs on prioritization of interdependencies and blockers.
• Experience and desire to work in a Global delivery environment