Support:Project Management: Difference between revisions

Jump to navigation Jump to search

Support:Project Management (view source)

Revision as of 14:01, 1 June 2017

4,809 bytes added ,  1 June 2017
no edit summary
(Created page with "'''Disclaimer: the processes described here might change as the project evolves. We will update this page each time something changes. ''' '''Audience''': Anyone who is intere...")
 
No edit summary
Line 1: Line 1:
'''Disclaimer: the processes described here might change as the project evolves. We will update this page each time something changes.
'''Disclaimer: the processes described here might change as the project evolves. We will update this page each time something changes.
'''
'''
'''Audience''': Anyone who is interested in participating in the SUMO project.
'''Audience''': Anyone who is interested in participating in the SUMO project.


Line 7: Line 8:
= Component owners and Tools =
= Component owners and Tools =


For each functional area of the SUMO project we have component owners assisted by back-ups. Their main responsibilities are:
==Component owners==
For each functional area of the SUMO project we have [[Support/bugzilla-sumo-lithium-component-owners|component owners assisted by back-ups]]. Their main responsibilities are:


* Act as main point of contact and for their functional area.
*Act as main point of contact and for their functional area.
*Actively use and work with their functional area on a daily basis.
*Actively use and work with their functional area on a daily basis.
*Act as component owners in Bugzilla for their functional area.
*Act as component owners in Bugzilla for their functional area.
Line 22: Line 24:
You can find a full list of [[Support/bugzilla-sumo-lithium-component-owners|component owners here]]  
You can find a full list of [[Support/bugzilla-sumo-lithium-component-owners|component owners here]]  


== During a sprint ==
== Tools ==
* assignees to bugs for that sprint, move their bugs forward daily
The SUMO team uses a defined set of tools to manage projects, processes and conversations. These are:
== Followup at the beginning of every marketing sprint ==
 
* At the beginning of every marketing sprint (sprints last 2 weeks, so approximately every 2-2.5 weeks), the component owners should ensure that the bugs in their component are prioritized correctly and that all high priority bugs are moving forward.
*Trello: project management
* All: Try to zero your needinfos at the beginning of every sprint. If you can't, ask for help or needinfo somebody else or leave the needinfo if it's a low priority bug. Needinfos shouldn't be a burden. More important to move the current sprint, high priority bugs forward.
**Track and  monitor progress of projects
* All component owners: Once every six months (e.g. at All Hands) look at bugs that are: '''WONTFIX AND component: feature request or severity: enhancement''' and see if they need to be re-opened.
**Assign tasks to people
**Handle multiple projects at one time
**Track and monitor sprints
 
*Bugzilla: issue reporting and tracking
**Report and track issues
**Assign priorities
**Triage
**Handle one issue only per bug. Any other issues need separate bugs.
**Rule of thumb: bug comments should be related to the reported issue only. Anything more extensive than that should either be broken up in several bugs or moved to a forum thread discussion.
 
*Forum threads: discussions
**Normally when issues/solutions are not very straightforward we start with a discussion to figure out what needs to be done. Once that is figured out then we file bugs accordingly.
**One can also start with a bug and then move to a forum discussion if the issue is complex and requires extensive research/discussion.
 
*Google docs: documentation
**Consolidate main points, conclusions and decisions from a forum thread discussion
**Document project plans
**Spec out feature requirements
**Consolidate feedback
 
Depending on the project other tools might be added and used depending on the requirements of the specific project (e.g. GitHub, Moqups etc). These will be clearly specified in the project’s Trello board under “Project Info”.
 
=Project, process and bug management=
 
As the rest of the Marketing org, the SUMO team operates in 2 and a half weeks sprints. All the information around current projects, activities and sprints can be found in the following Trello boards:
 
SUMO Roadmap board
Lists all the current projects and organizes them as per estimated completion time.
Some projects do not have an agreed completion time yet, these will be listed as pending.
Each project has somebody assigned to it as the owner. That person is responsible for updating all the documentation, tasks, bugs, discussions related to that project. He is the go to person for any questions.
The “Ideas” card lists all projects/ideas/suggestions that did not make it to the roadmap yet.
Each project card should contain the following:
Name of the project
User story/Goal (What are we trying to achieve)
Link to Project Board
Project Owner (who drives this) - this is done by assigning a member of the team to the card.
 
The Roadmap Trello board is maintained by Madalina. Please contact her if any information is missing or if you have any questions.
 
SUMO Project board
Each project has its own public Trello board. You can access it by clicking the link listed under the project card in the Roadmap board.
A project is usually spread out across multiple sprints!
 
Each project board will contain the following lists of cards:
Project Info
User Story/Goal of the project (what are we trying to achieve)
Timeline (when do we expect this to be finalized)
Acceptance criteria (what needs to be completed to mark this project as done)
Tracker bug (if any)
Discussion thread (if any)
Documentation (Google Docs, Git etc)
Risk log (if necessary)
Anything else that is relevant
 
To Do
All relevant bugs
All relevant tasks or user stories related to this project
 
Doing (Queued for Sprint)
All cards that are being currently worked on (cards in this list will also be present in the Current Sprint board
 
Done
All cards that have been finalized
 
The Project Trello boards are maintained by each project owner. You can find the project owner by checking the project card in the Roadmam Trello board. Please contact the project owner directly if any information is missing or if you have any questions.
 
Current Sprint Trello board
 
A sprint usually contains bugs/user stories from several projects!
This board is tracking all the activity of the current sprint. It has the following card lists:
 
About this sprint
Information about the current sprint
Agenda of the sprint planning meeting
Risk register
 
Backlog
All bugs/users stories that were marked as P1s but did not make it to the current sprint yet
 
Push to Lithium support
All bugs/user stories that cannot be fixed by ourselves and were pushed to Lithium support queue
Blocked
All bugs/user stories that are currently blocked
In progress
All bugs/user stories that are being worked on in the current sprint
Ready to be verified
All bugs/user stories that have been finalized but need to be verified
Done
All bugs/user stories that are done.
The Current Sprint board is maintained by Madalina. Please contact her if any information is missing or if you have any questions.
 
Lifecycle of a SUMO Sprint
 
A SUMO sprint takes 2 and a half weeks. It always starts on a Monday and finishes on a Wednesday.
 
We do a round of bug triaging before each sprint.
 
Thursday (4 days before the sprint starts)
We hold the sprint planning meeting during the Platform meeting.
Retrospective of the previous sprint
Bug and user story prioritization
Agree on bugs/user stories to be worked on during the next sprint
Update current sprint Trello board and assign owners
Monday
Sprint starts
Project owners are responsible for updating their project boards accordingly
 
..2 weeks later
 
Monday
Madalina sends reminder sprint is ending
Madalina sends reminder to bug component owners to do another round of triaging
 
Wednesday
Sprint ends
MarCom sprint demo
 
Thursday
New sprint planning meeting
 
Sprint Planning
Q2 Sprints
Sprint 3, starts May 15, ends Wed May 31, 2017
Sprint 4, starts Monday June 5, 2017, ends Wed June 21, 2017
 
 
Q3 Sprints
Sprint 1
No info yet when this starts
Sprint 2
Sprint 3
Sprint 4
 
 


=== Q2 2017 Sprints ===
=== Q2 2017 Sprints ===
Madasan
Confirmed users
292

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1172422"

Navigation menu