How To Be a Project & Product Manager(II)

PM JZ.
3 min readMay 22, 2021

--

Photo by Jo Szczepanska on Unsplash

I decide to try the new challenge: To be a project manager as well as a product manager.

And I am ready for the worst thing happens: I cannot afford to take care of both project and product, I step back to product management again.

Why?

I hope to keep learning so that life would not be boring.

I always enjoy managing a project from scratch. Especially using Agile, one of the best practice I’ve ever seen and implemented. The first time I knew about this methodology was when I worked with a software development team — the workflow they implemented were neat, organized, highly-efficient, advanced, pretty impressive. It builds a framework to strength team spirit with transparency, trust, result-driven and agile, as well as provides an end-to-end lifecycle to track the whole-team’s performance with multiple metrics, encouraging team to grow with the achievements of iterations. Therefore, I decide keep implementing and practicing this method in the tech team I joined.

On the other hand, after talked with the experienced guys with product knowledge, I decide to step into the world of product. Digital transformation is becoming much more urgent for so many manufacturers and retails. Knowledge of product will provide a chance for me to deeply investigate a business pattern, and to keep searching for the value hiding in somewhere, for making our life to be more easier. Generally speaking, this field’s doorsill is pretty friendly, once someone steps in, there is an unlimited space for him to grow up.

Game starts when rules are settled.

A. Setup of Agile Project Management

According to my plan, different from the traditional workflow which was lack of organized and methodical thought. I will kick off the agile project management and product management as below:

  1. Began with workflow optimization regarding to the implementation of Story points, Sprint flow with meeting defined, project management tools setup(Jira, Confluence), performance metrics and DOD (Definition of Done).
  2. Align all of the rules with stakeholders.
  3. Implement and optimize along with the achievement of iterations.

B. Setup of Product Management

Once the agile methodology be on the right track, I started the setup of the product-related rules.

  1. Product definition: what is it? What has been done? What will it be like?
  2. Roadmap and milestone of the product development: features that are valuable for users, requirements that business stakeholders request, essential components that I should liaison with support dep. to collect.
  3. Milestones definition during a sprint regarding to the requirement collection, requirement confirmation, technical options and development. Input, output and stakeholders should be defined clearly enough.
  4. Align with all of the stakeholders to be acknowledged about the rules, optimization may happen if stakeholders provide constructive advices.

Always remember, rules setup is the easiest thing, the most challengeable thing is, to convince people to accept your rules and make everything goes the way that you want.

--

--

PM JZ.
PM JZ.

Written by PM JZ.

5-year-old PM, keeping playing and learning

No responses yet