In a project management sprint, multiple activities are happening all at once – new features are being added, improvements are being made to existing features, bugs are getting fixed – tasks run the gamut. Managing this process and keeping up to date on progress is, at once, both imperative and daunting.
Because so much happens within a sprint, Spotlight’s functionality allows users to accurately track progress every step of the way. In the initial stage of planning, specific tasks will be laid out and assigned to distributed employees, appearing in a list in the Message Center. There are no QA flags on tasks that are not started, tasks that are in progress, or tasks that are paused. When a task has been marked as completed in the Status column, the QA flags become visible. There are three different QA flags:
- Red indicates that the task is completed and ready for QA
- Yellow indicates that the task in being tested, and automatically tracks time for that tester
- Green indicates that the task has been approved
Alternatively, if the task is not approved, the tester can choose the “Re-opened” option in the drop-down box in the Status column, alerting the developer of the task’s changed status. The tester also has the option to open the task and comment on the changed status. When a task is re-opened, the QA flags disappear once again.
QA flags clearly display the progress of all the tasks, allowing users to see which tasks need to be QA’d, which are in progress, and which have been tested and approved.
Vincent Serpico: Good morning, everybody, and welcome to the webinar. We are going to go over the new QA flags and the bug tracking in Spotlight, a new feature that we are very, very excited about.
First thing, I need to change my status. I’m going to change my status to “in a webinar.” I am busy, and will be into this webinar until, let’s say, 11 AM. We’ll call this a meeting. Fantastic.
Let’s go over the new QA flags and bug tracking in Spotlight. Let me just give you a bit of history about on how we arrived at our above tracking and our QA flags.
First of all, during a sprint, you’re going to be adding new features. You’re going to be adding improvements to existing features. You’re going to be fixing bugs, and you’re going to adding other tasks, as well.
Everything happens within a sprint. When a task is set to completed, QA flags will display. Notice that there are no QA flags on tasks that are not started, tasks that are in progress, and any tasks that are paused, don’t have any QA flags.
QA flags are only on display on tasks, bugs, features, or improvements that are marked completed. They display as red, signifying that the task, bug, feature, or improvement is ready for QA.
Once it’s ready for QA, the QA tester, in this case it’s Kristen Simmons, will come in and mark the QA flag yellow. Yellow means that it’s currently being QAed.
Also, this is very important, this system will begin recording time for Kristen testing this task. It is 10:11 AM, where I am right now. This system is currently recording the time for Kristen QAing this task over here.
Once completed, once it passed QA, Kristen can then mark the task as approved and green, or if the task is not approved, she can flip it back open to reopen.
Notice the QA flags will go away, and the task is not reopened. Norman will get an alert that his task has been reopened. Presumably, Kristen will go into the task, and leave a comment as to why it’s reopened.
Actually, let’s go ahead and mark this as completed again. We feel that the QA flags are a very easy way to quickly see the progress of all the tasks. Let’s say, I want to do a filter on everything that has been completed. After all, that’s where the QA flags are set on.
Out of all the completed tasks, I can see that there are still several that need to be QAed, and still several that are in progress, and several that are already tested and approved. I can quickly scan down and get an idea of where we are with all of the QA testing. We feel that’s a very, very efficient way to manage QA, keep QA as a first class citizen, and stay involved with everything going on at the development level.
I like to keep these webinars short. I like to keep them to the point. Everybody has very, very busy days. As always, the webinar will be posted on our website for further review. Again, we try to keep them very short, 10, 15 minutes, and followed by a round of Q and A.
I’m going to open it up to Q and A right now. If you have any questions, please go ahead and type it in the questions area. I’ll go ahead and get them answered. Other than that…
OK, I see a question right now about marking a QA flag as yellow. Yes, it does track time. The time tracking works exactly the same as a time tracking on a status update.
If you mark a QA flag as yellow and your status is away or offline, it will not track the time. If you mark a QA flag as yellow and your status is busy or available, then yes, it will track the time.
Of course, it will track the time for the person who is assigned as a tester to the task.
Another question, no, a comment. Yes. Thank you. Thank you very much.
We feel that the integrated approach is quick, easy, to the point, and just gets the job done. Thank you very much for attending the webinar. We’ll see you next week. Bye‑bye.