Description

We need to track better the milestone quality.

Goals

Propose a transparent process for managing the Milestone-relevant bugs in Bugzilla. - Transparency on the delivery - Clear current Responsibility - Clear TPM responsibility - Clear current assignee

Resources

No special resources Bugzilla,

Questions to answer:

What is the best way to track the responsibilities on the tickets, including those of the technical project managers, developers, and subject matter experts?

Looking for hackers with the skills:

milestone tracking quality improvement improve project

This project is part of:

Hack Week 24

Activity

  • about 1 month ago: rtsvetkov joined this project.
  • about 1 month ago: stripathy liked this project.
  • about 1 month ago: stripathy started this project.
  • about 1 month ago: rtsvetkov added keyword "improvement" to this project.
  • about 1 month ago: rtsvetkov added keyword "improve" to this project.
  • about 1 month ago: rtsvetkov added keyword "project" to this project.
  • about 1 month ago: rtsvetkov added keyword "milestone" to this project.
  • about 1 month ago: rtsvetkov added keyword "tracking" to this project.
  • about 1 month ago: rtsvetkov added keyword "quality" to this project.
  • about 1 month ago: rtsvetkov liked this project.
  • about 1 month ago: rtsvetkov disliked this project.
  • about 1 month ago: rtsvetkov liked this project.
  • about 2 months ago: rtsvetkov originated this project.

  • Comments

    • hennevogel
      about 1 month ago by hennevogel | Reply

      Milestones of what exactly? :)

    • rtsvetkov
      about 1 month ago by rtsvetkov | Reply

      Project ;) In this case, it is mostly a BCL product project: Such as SLES15 ,16 or Micro

    Similar Projects

    Yearly Quality Engineering Ask me Anything - AMA for not-engineering by szarate

    Goal

    Get a closer look at how developers work on the Engineering team (R & D) of SUSE, and close the collaboration gap between GSI and Engineering

    Why?

    Santiago can go over different development workflows, and can do a deepdive into how Quality Engineering works (think of my QE Team, the advocates for your customers), The idea of this session is to help open the doors to opportunities for collaboration, and broaden our understanding of SUSE as a whole.

    Objectives

    • Give $audience a small window on how to get some questions answered either on the spot or within days of how some things at engineering are done
    • Give Santiago Zarate from Quality Engineering a look into how $audience sees the engineering departments, and find out possibilities of further collaboration

    How?

    By running an "Ask me Anything" session, which is a format of a kind of open Q & A session, where participants ask the host multiple questions.

    How to make it happen?

    I'm happy to help joining a call or we can do it async (online/in person is more fun). Ping me over email-slack and lets make the magic happen!. Doesn't need to be during hackweek, but we gotta kickstart the idea during hackweek ;)

    Rules

    The rules are simple, the more questions the more fun it will be; while this will be only a window into engineering, it can also be the place to help all of us get to a similar level of understanding of the processes that are behind our respective areas of the organization.

    Dynamics

    The host will be monitoring the questions on some pre-agreed page, and try to answer to the best of their knowledge, if a question is too difficult or the host doesn't have the answer, he will do his best to provide an answer at a later date.

    Atendees are encouraged to add questions beforehand; in the case there aren't any, we would be looking at how Quality Engineering tests new products or performs regression tests

    Agenda

    • Introduction of Santiago Zarate, Product Owner of Quality Engineering Core team
    • Introduction of the Group/Team/Persons interested
    • Ice breaker
    • AMA time! Add your questions $PAGE
    • Looking at QE Workflows: How is
      • A maintenance update being tested before being released to our customers
      • Products in development are tested before making it generally available
    • Engineering Opportunity Board