Tabagile Scrum Board

1 (alpha version), is a simple scrum board that will help you, a Product Owner, to deal with your stories, sprints and your team members.

1 alpha features:

• All members work as a team to manipulate the list under “Manage”.

• Each member can see what’s really important.

• Scrum players are in Sync with WordPress Roles and Capabilities.

• You can insert entries as Stories, Epics, Themes, Tasks or Project.

• Tabagile Scrum Board permits you to maintain the relationships between the entryes. That is, an Epic can be a parent category for a lot of stories, for example.

• Set the stories as “Not-ready” or “Ready” and submit them to sprint. Trac it all.

Next alpha release features:

• Entries pagination and a “sort by” the table title names.

• View the entries according by the relationship beetween them(parents and children nodes).

• Request for approval using e-mail on changing the entry status.

• Visualize the graphs for “release burn-down”, “sprint burn-down”.

• Attach files and documents to the entries.

• Setup the title table names that will be shown in the product backlog list

Tabagile Scrum Board is a variant derived from Abstract Dimension’s Todo List Plugin.

Roles and Capabilities

• “subscriber” / role:0 = Client (that user can sugest stories directly in the product backlog, trough a public interface, and can follow entries created by himself)

• “contributor” / role:1 = Team Member(that user can sugest stories directly in the product backlog, trough a public interface, and can follow entries created by himself)

• “author” / role:2,3,4 = Team Member (that user can see your tasks in product backlog)

• “editor” / role:5,6,7 = Scrum Master (can dealing with tasks and team members)

• “administrator” / role:8,9,10 = Product Owner (can dealing with epics, stories, themes, projects and grant access for all team members)

Table Structure

• id bigint(20) NOT NULL auto_increment: the entry id ( story, epic, theme )

• idParent int(11) default NULL: parent id number, if it exists

• sprintNumber int(11) default NULL: sprint number that will support the storie

• points int(11) default NULL: story points

• author bigint(20) NOT NULL default ‘0’: story account id

• att bigint(4) NOT NULL default ‘0’: attendant id (scrum-master, p.o, team-member)

• targetActors bigint(20) NOT NULL default ‘0’: the target profile that will be

• tasktag bigint(4) NOT NULL default ‘0’: it will show you if the entry is a ‘0 = story’, ‘1 =

epic’, ‘2 = theme’, ‘3 = task’, ‘4 = project’

• status tinyint(1) NOT NULL default ‘0’: this field is abble to show you if your story is ‘0 = notset’, ‘1 = notready’ ‘2 = ready’, ‘3 = progress’, ‘4 = has been done’

• priority tinyint(1) NOT NULL default ‘0’: ‘0 = important’, ‘1 = normal’, ‘2 = low’

• todotext text NOT NULL: The full entry description

• created_at datetime NOT NULL default ‘0000-00-00 00:00:00’: The date that the entry has been created

• starts_in datetime NOT NULL default ‘0000-00-00 00:00:00’: The date that the entry was submited to the sprint

• ended_in datetime NOT NULL default ‘0000-00-00 00:00:00’: The date that the entry has been doned