Role: Technical Product Manager/ Scrum Master.

Location: New York, City 5 Manhattan West (Day 1 Onsite)


Role Technical Product Manager/Scrum Master that includes 3 areas:

 


1/3 - Project Management / Scrum Process·       Capable of synthesizing
information and pulling together accurate and well synthesized management
reports:

·       Need to be able to report on Obstacles/Issues in a meaningful and
accurate way to management so a quick remediation can occur to move our process
along.

·       Also need to be able to report on value generated in a meaningful way
& Publish weekly metrics on progress made based on verified state changes. 
 For Example NEW (@WIP) to NEW (without the @WIP tag) or UNDER REFINEMENT to 
READY.   The statuses should only be reported on if the definition of ready and
definition of done has been validated as per above workflow.   Specifically ?

·       # of Scenarios total & changed since last report that are available
 to be groomed in the backlog (NEW (without the @WIP tag)

·       # of Scenarios total & changed since last report that are groomed in
the backlog, and ready for review (READY)

·       Etc.

·       Is responsible for ensuring the Workflow / Processes meet the
definition of done when moved from one status to another status in JIRA.   This
should be done in a timely manner and no JIRA should be unchecked for more than
24 hours.

·       Is responsible for tracking when a "Status" does not meet the
"definition of done", and holding the person accountable for repeatedly moving
a JIRA to a status not meeting the definition of done.

·       Is responsible for facilitating the joint meetings needed to move
JIRAs from certain statuses to another ? these require accurate agendas, and
excellent meeting management skills to cover a big agenda in a short amount of
time.  

·       Needs to be well prepared for meetings with all relevant data and
ensure the data is accurate before presenting it.

·       Is responsible for ensuring that all BLOCKED JIRAs have associated
defects / issues linked to them, and that those linked issues have been accepted
 by the assigned team.   Accepted means:

·       Triaged and documented for root cause (not proximate cause)

·       de-duplicated with any existing issues

·       accepted by the team as their issue

·       assigned for resolution

·       has a timeframe for resolution and there is a reasonable path to
unblocking the JIRA

·       Is responsible for escalating when Blockers do not have a reasonable
plan for resolution in a reasonable timeframe.  Reasonableness is relative to
severity.

·       Is responsible for ensuring every JIRA story has a groomed epic.

·       Is responsible for a groomed backlog, with JIRAs that follow the
process / standards.

·       Is responsible for a  force ranked JIRA backlog with every JIRA and
JIRA status validated to ensure it meets the standards.  

·       At any point in time, the JIRA backlog is up to date, without any
"work" required to bring it current

·       The Kanban board is always accurate showing JIRAs in each JIRA status
& tagging state.

 


1/3 - ++Ability to analyze data and requirements in a product. 
Groom stories / apply standards to the definition of done.
Understand technical applications and root cause of errors
Differentiate proximate cause from root cause
See patterns in data and investigate possible error patterns for insights. 




1/3 - ++Ability to run tests to validate they are working or not
(competence in unix / flows). 
Be able to use the product using the CLI
Be able to view and analyze logs for obvious errors or pressure test
hypothesis.
Be able to use Bitbucket/Git to make changes