This document outlines the product method used by ForceManager which follows a Scrumban approach. It involves conducting user research and design, estimating work, defining features and scope, development in sprints, quality assurance testing, and releases. The team roles include the product owner, UX/design team, QA team, development team, and a rotating scrum master. Key performance indicators such as velocity and meeting frequency are tracked by sprints.

2. The product method
Product chain

3. Index – ForceManager Product Method
3

4. Index – ForceManager Product Method
1. User Research Interviews
2. Validated Designs
SPRINT 1
3. Estimate
4. Feature Scope
5. Investments
SPRINT 2
6. Development
7. Quality Assurance Revision
8. Release SPRINT 3
4

5. 1. User Research Interviews
SPRINT 1
Responsibility
• Get from the Stakeholders the feature requirements
Participants
• StakeHolders
• Product Owner[s]
• UX/UD Team Member[s]
Output
• Feature requirements
5

6. 2. Validated Designs
SPRINT 1
Responsibility
• Generate wireframes/prototypes following the stakeholders
requirements
• Generate specifications following the stakeholders requirements
Participants
• StakeHolders
• UX/UD Team Member[s]
• Product Owner[s]
Output
• Feature wireframes or prototype
• Feature specifications
6

7. 3. Estimations
SPRINT 1
Responsibility
• Development team evaluation related to the feature specifications
Participants
• Product Owner[s]
• UX/UD Team Member[s]
• Development Team Member[s]
• Quality Assurance Members[s]
• Infraestructure Team Members[s]
Output
• Feature estimations
• Feature Risk
• Investment Plan
• Quality Assurance Plan
7

8. 4. Feature scope / versioning
SPRINT 1
Responsibility
• Define the scope of the feature for all the versions
Participants
• StakeHolders
• Product Owner[s]
Output
• Feature roadmap
• Development calendar
8

9. 5. Investments
SPRINT 2
Responsibility
• Execute the investments included on the investment plan
• Iterate the estimations
Participants
• Product Owner[s]
• Development Team Member[s]
• Infraestructure Team Members[s]
Output
• Estimations
• Development calendar
9

10. 6. Development
SPRINT 2
Responsibility
• Develop the feature according to the scope specifications and designs
• Release a tested code
• Log the work progress
Participants
• Development Team Member[s]
• UX/UD Team Member[s]
• Infraestructure Team Members[s]
UNIT TESTING
Output
• Feature tested (*) to be certified
INTEGRATION TESTING
• Log of work
ACCEPTANCE TESTING
10

11. 7. Quality Assurance Revision [1]
SPRINT 3
Responsibility
• Exploratory Testing over the product front-ends
• Generate Bug/Improvements for the development Team
Participants
• Product Owner[s]
• Quality Assurance Member[s]
Output
UNIT TESTING
• Product[s] plan execution result
• Kanban Tickets INTEGRATION TESTING
ACCEPTANCE TESTING
11

12. 7. Quality Assurance Revision [2]
SPRINT 3
Responsibility
• [Web, Server] Deploy the product on pre-production environment
• [Mobile] Release a release candidate and test with real customers
• Check the compliance of the product
Participants
• Product Owner[s]
• Quality Assurance Member[s]
• Infraestructure Team Members[s]
UNIT TESTING
Output
• Product approved INTEGRATION TESTING
ACCEPTANCE TESTING
12

13. 8. Release
SPRINT 3
Responsibility
• Release a tested and stable product to PRODUCTION
Participants
• Product Owner[s]
• Infraestructure Team Members[s]
Output
• Product released
13

14. SCRUMBAN
The team method

15. Team Responsibilities
Product
Manager
Product Owner
Scrum Team Members Force
SPRINT • User Experience Experts Manager
Backlog • Quality Assurance Experts
• Developers / Engineers
Product
Backlog
KANBAN
Backlog
Scrum Master
• Agility “Guardian”
• Team leader
15

16. Team members responsibilities
Product Owner
• Stakeholders agent in front the development team. Every requirement
must be channel through him
• He must keep the product backlog and prioritize and decide which tasks
will be included in the Sprint backlog or as a Kanban ticket
• Finally must revise the output products with the Stakeholders
(sometimes himself if the product owner is the product manager)
UX/UD Team
• UX / UI Expert who manage the prototyping, wire-framing getting the
users requirements and expectations
• Provides to the development team the UI checked with the
customer/stakeholders
16

17. Team members responsibilities
QA Team
• Define Quality Plans
• Product Quality Responsibility
• Block / Authorize the release of the product versions
Development Team
• They’ve the responsibility to deliver the product output planned for
every SPRINT, updating the Backlog status and, in general, following the
organization quality and process guidelines
• StandUp meeting
• Log of Work
• Integration and Unit testing
• Code documentation
17

18. Team members responsibilities
SCRUM Master
• Developer Engineer who implies the rest of the team to follow the
guidelines have been agreed by the organization
• SM check the following of the team guidelines
• Ensures the team is fully productive (Remove Barriers…)
• Ensures the team follow the process (Version Control Policy, Log
Of Work, ALM flow…)
• Manage the state of the Cardwall and the daily StandUp
• Report to the Product Owner the progress of the SPRINT
• Include new guidelines could improve the team behavior
Our organization will not have any specific SM, all of us will be the SM in at
least on of the sprints of the YEAR.
18

19. Development Team Insights/KPI
For every SPRINT we will store the next KPI :
• % Capacity Reported: Log Work / Total Work Capacity
• % Achievements: Closed Work / Total Plan Capacity
• Velocity: Closed Work (hours)
• % StandUp Meetings: #StandUp / #DaysInSprint
Is the responsibility of the Scrum Master to work to maintain good results for
this insights and report them to the product owner at the end of the
SPRINT.
19

20. ¡Thank you!
ForceManager Team