wiki:INTERNAL_BACKLOG_STRUCTURE_R1

Version 15 (modified by todor, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=INTERNAL_BACKLOG_STRUCTURE_R1, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

This revision should make the internal backlog easier to use.

Task requirements

  • This task depends on SCS_WIKI_MAINTENANCE_R2 Make sure you implement it after the maintenance.
  • Use the existing structure of the backlog
  • Define rules of backlog (using previous revision implementation INTERNAL_BACKLOG_STRUCTURE_R0 Create a wiki page, create a link to it in SCS_SITE_DESIGN/DevelopmentHome page.
  • Research forms (an example is added as comment in the ticket) to provide a way to post quick impediments, open questions, etc (without signing in). Link created forms in SCS_SITE_DESIGN/DevelopmentHome
  • Correct dates to the following date format YYYY-MM-DD
  • Remove the milestone rows as they are not accurate (daily availability sheet)
  • Resize the columns for their content
  • Add "Assigned to" and "Comments" column to the impediments sheet
  • For daily availability set format for the availability columns and apply it (See implementation idea section for this one).
  • Decide which sheets should have Comments columns and add them
  • Add "Solution" columns to open questions and impediments sheet
  • Fill in the Important documents and define a way to mark when they are changed

Task result

More usable backlog

Implementation idea

The easiest way to accomplish correct date formatting is to select the entire column and click the More formats button (Looks like this: [123]). Took about 30 minutes to find it out! Create forms for impediments and open questions.
List of important documents: ImportantDocs

INTERNAL_BACKLOG_STRUCTURE_R1
​http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en

How to demo

Show ​http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en and explain modified parts.

Design

  • Discussions were made, to come up with some of the following things.
  • Forms were decided to be obsolete.
  • Improve Daily Availability spreadsheet
    • Remove the blank separators from the daily availability, because they're obsolete and create difficulties in filling the availability.
    • Add columns for all missing team members
    • Each member must have two columns:
      • the first is for description of the time interval he/she would be available
      • the second column contains the total time measured in hours that the team member will work on this date
      • you may add different backgrounds for easier navigation in the backlog
    • Replace the colors with text, where is green replace it with "1eff"
    • Fix the file format it must be YYYY-MM-DD
  • Impediments spreadsheet
    • add column for comments
    • add column "assigned to"
    • add column "Solution"
  • Open questions spreadsheet
    • add column "Solution"
    • delete "Assigned to" column, it is obsolete
  • Smells spreadsheet
    • add column for comments
    • add column "assigned to"
  • Documents spreadsheet
  • Resize all columns to fit their contents
  • Create document with detailed explanation of the internal backlog's contents

Impediments

Name - contains short descriptive name of the impediment written down with small letters and "-" instead of spaces.
Description - contains more detailed (most of the) information about the impediment. It may contain several sentences.
Date - this field must contain the date that the impediment is discovered. You must submit the impediments at the moment you saw them, so ideally this field includes the date when the impediment was submitted.
Reporter - contains the dev id of the one that has discovered and reported the impediment.
Impact - contains information about how severe the impediment is. There are three possibilities: low, medium and high.
Status - there are two possibilities: resolved - if the problem is solved, and unresolved - if the problem is still on line.
Assigned to - this field is optional and includes the dev id to the team member that is assigned to resolve the impediment.
Comments - this column includes comments about the impediment. All team members can write a comment, it is recommended if you have opinion on the topic to leave a comment.

Smells

Name - contains short descriptive name of the "smell" written down with small letters and "-" instead of spaces.
Description - contains more detailed (most of the) information about the "smell". It may contain several sentences.
Location - contains information about where the "smell" is located.
Date - this field must contain the date that the "smell" is discovered. You must submit the "smells" at the moment you saw them, so ideally this field includes the date when the "smell" was submitted.
Reporter - contains the dev id of the one that has discovered and reported the "smell".
Status - there are two possibilities: done - if the problem is solved, and open - if the problem is still not solved.
Assigned to - this field is optional and includes the dev id to the team member that is assigned to resolve the "smell".
Comments - this column includes comments about the "smell". All team members can write a comment, it is recommended if you have opinion on the topic to leave a comment.

Documents

Categories - Documents are separated in three different categories: SETUP, PROCESS, PRODUCT. Each include documents that are useful and must be read.
Document - this column contains the name of the document.
Link - provides link to the document.
Last Update - contains the date on which the document was last modified.
Description - contains short description about document purpose and contents.
dev id - contains the date that each team member has read the document for last time.

Daily Availability

Date - this column contains the corresponding date.
dev id - Desc - contains the description of the period for which the team member will be available. For example between 12h and 17h.
dev id - Time - contains the amount of hours that the team member will be available this day. For example 5h.

Open Questions

Question - contains the open question.
Date - this field must contain the date that the question appeared. You must submit the open questions at the moment you saw them, so ideally this field includes the date when the open question was submitted.
Impact - contains information about how important the question is. There are three possibilities: low, medium and high.
Status - there are two possibilities: done - if the question is answered, and open - if the question is still not answered.
Solution - contains detailed answer to the question.

Implementation

(Implementation results should be described and linked here (from the wiki or the repository))

Testing

Comments

(Write comments for this or later revisions here.)