It's a product management kind of day

It's a beautiful Friday afternoon and I am in the land of product managers. It's really interesting that open positions seem to come in waves. There have been many times in my career where I have found myself in this situation. I have experienced it with technical trainer, business analyst, quality assurance, and many other roles. It actually makes my job more manageable; I can search for one skill set instead of three or four at a time. Also, it makes it much easier for me to present candidates to multiple opportunities, increasing my chances of placing them in that coveted J-O-B. I would be interested to hear if anyone in the job market has had a similar experience. Do you have days with lots of new jobs to apply for and other days when there is nothing?

Currently, I have 5 Product Manager positions open. 2 of these roles are contract and 3 are direct hire. A break-down is below:

#1: Product Manager; San Francisco, CA, 4 month+ contract, Online Community experience is required
#2: Product Manager; Walnut Creek, CA, 3 month+ contract (possible contract to hire), IA, User Testing & SCRUM experience is required
#3-5: Sr. Product Manager: San Francisco, CA, Direct Hire/Perm, health care and Agile experience is preferred

As always, you can contact me at aclark@kforce.com or 415-678-2321.

- BG Recruiting

New Job - Agile Product Manager - Walnut Creek

My client is seeking an experienced Agile Product Manager to join their growing team. This is a 12 month+ contract in Walnut Creek. If you are interested, please contact Aileen @ aclark@kforce.com or 415-678-2321.


The Product Manager represents the Product Owner and the End-User/Customer – they are responsible for defining and scheduling the delivery of high quality output in line with business requirements and priorities.


Key Responsibilities of the Product Manager (Scrum Meetings):


• Meet with business stakeholders to discuss, define and capture requirements – User Research
• Consider Market conditions
• Manage the Product Management documentation- Product Backlog(s), Release Plan(s), Product Roadmap(s), Release Notes and any other Requirements-level notes/sketches
• Communicate and capture requirements in a way that people can understand them e.g. Themes, Epics, User Stories, Test Cases, UI sketches, Conditions of Satisfaction etc.
• Presentation of new user stories/requirements (this may also be done by the Product Owner)
• Document feedback from the development team (e.g. viability of stories and top-level effort estimates)
• Re-prioritize, expand and more clearly define the product backlog
• Add/remove user stories and conditions of satisfaction as necessary
• Introduction of user stories and agreed conditions of satisfaction to the development team
• Document level of effort estimated to deliver each user story – use these to drive prioritization and release planning
• Present the highest priority User Stories – and suggest the proposed scope of iteration (this may be done by the Product Owner)
• Negotiate top-level Sprint scope and ensure that requirements are fully understood
• Agree Sprint Objectives with development team – this is a collaborative process
• Update release plan further to the meeting and ensure that the Product Owner (and Key Stakeholders where appropriate) are aware of the Sprint scope

Requirements:


• Experience writing Stories, prioritization, effectively communicating with Development team
• User Research: i.e. Experience creating User Journeys
• Understand web development
• Understand data flow
• Understand how to create structures and systems
• Experience with JIRA and/or Rally
• Experience with Balsamiq
• Team uses Mac, so that would be a plus to have
• Usability Testing is nice to have


- BG Recruiting