☀️ Good afternoon forks, after a long public holiday in Thailand, it’s time to back to a serious mode 🤔. Therefore, today I’d be in a seriuos mode with the CSPO training note.
A big goal of this class is to prepare all of participants to be a GREAT Product Owner out in the real world!!!
According to my previous article about choosing a CSPO course, after that I attended the class and would like to write down the things I learned from the class here:
1. Project Development Processes
Starting with an introduction of running a project with “Defined Process VS Empirical Process”. my classmates and I did a think-pair-share activity to discuss about pros and cons of each process, then the instructor summarized and pointed out the key differences of both — my recommended article about defined vs empirical process — in case, you’d like to see an easy understanding and simple explanation, I would highly recommend to enroll a CSPO training session with Pete Deemer 👉here
Scrum is a tool for producing Transparency to enable Inspect and Adapt — by Pete Deemer 👍👍👍
2. All about products
What’s Product? — products are things we’re producing or developing e.g. mobile application, marketing plan, upgrading a platform, etc.
Product Goal(s) — Things, features, benefits, or any outcomes that contribute values to customers or users or solve the users’ problems.
Product Backlog Items (PBIs) — Whatever a team needs to know to achieve the product goals i.e. stories, features, changes, etc. The PBIs can be written in any format such as user story in a card with; as a…. I want to… so that…, wireframes, use-case, functional specs, technical specs, background, etc. It will be used to communicate and collaborate between product owner and developers. Strive to create conversations between product owner and developers to keep the team work toward the same goal. Besides that the team will discuss and confirm about the business conditions/ constraints, pre-requisites, expected results and acceptance criteria.
Product Backlog — A queue or a list of PBIs; usually arranged from top priority (from a PBI item contributes the biggest to to the smallest values, or prioritized from the most important things to do to achieve the product goal, to could have things but they’re unnecessary to do now)
Self-organizing team — A team includes three main roles, as follows, product owner( or PO, the one who knows what are the users’ problems, what are the goals to achieve, and tradeoffs between scope<> schedule<>cost <> quality), developers (not only a group staff who develops or producing the products, it’s also including designers, testers, others specialists in related domain(s), and whoever that the team needed to participate with any step(s) of producing the product) and scrum master (a teacher or a coach for a scrum team who will help and support the team to overcome any setback or obstacle, improve efficiency while running a project). Responsibilities of the self-organizing team is to manage themself to do the day-to-day tasks to achieve the product goals.
There is no boss in a self-organizing or scrum team
3. The Sprint
Sprint Goal — The target of the team needs to be achieved within a sprint period (the most popular one is 2-week sprint). Note: It should be clear and realistic.
Sprint Planing — Developers will estimate how long does it take to complete each tasks (and sum up PBI implement time by PO) by the end of sprint by review each task/PBI.
Daily Scrum — Recommended not to exceed 15 mins, the objective of daily scrum is to get to know of what tasks were done and what’re the next tasks by each developer
Product Increment — What is the team done thoroughly that aligned with the product goal
Sprint Review — this review activity is focusing on Product which will agree together with scrum team and stakeholders (i.e.: users, customers, managements, sponsors, etc.) Aiming at examination the outcome whether it is still right or still relevant with the product goal, unless the teams will discuss and adapt the development ways or make adjustments the product (in backlog) and/or the team members until achive the product goals.
Recommended rules or prohibit actions during run a sprint are:
— Don’t change the sprint goal(s)
— Sprints are never extended
— PO can terminate the sprint
Undone task(s) — If there any undone task at the end of the sprint, the product owner will put the undone task list back to the product backlog, then remove the tasks from the bottom list. Since the team has limited resource, then the PO need to tradeoff between undone tasks and PBIs with lower values.
4. Product Backlog Refinement or Grooming
Product Refinement backlog refinement — Breaking down large PBIs into smaller PBIs. The smaller items will contain further detailed that the team getting clear and can work on it. Note: After splitting, the customer values of the PBIs have to be the same.
Scope Buffer or Sprint Buffer— the PBIs that contribute lowest value to customers and/or business. PO can use these PBIs to do bug fixing or do any prove of concept things. For instance, using the scope buffer to do the defect-fixing of the higher value PBIs, then PO can drop the lowest value PBIs off for this release.
That’s all for my note on the first training day 🤓😂
Wanna read more? 👉 CSPO training Day 2
