PROJECT STORY BOARD TO BOARD COMMUNICATION TOOLS
Systems and methods provide for hosting one or more server computers comprising a project management software. The project management software may comprise a first story board comprising one or more stories for a first team. The first story board may be controlled by one or more first story board control panels. The project management software may also comprise a second story board comprising one or more stories for a second team. A sub-story may be created using the one or more first story board control panels. In one embodiment, this sub-story may be inserted into a backlog list for the second story board and an alert may be displayed on the second story board requesting the second team to implement the sub-story from the backlog list into the second story board. In another embodiment, the stories on the second story board may be about, but not used by, a second team. The first team may be responsible for updating the one or more stories to move the one or more stories, including the sub-story, through the second story board.
1 . A system, comprising:
a) a project management software hosted on one or more server computers communicatively coupled to a network;
b) a first story board within the project management software comprising one or more stories for a first team;
c) a second story board within the project management software comprising one or more stories for a second team;
d) one or more first story board control panels within the project management software configured to:
i) create a sub-story; and
ii) insert the sub-story into a backlog list for the second story board responsive to creation of the sub-story; and
e) an alert, displayed on the second story board, requesting the second team to implement the sub-story from the backlog list into the second story board.
2 . The system of claim 1 wherein at least one of the one or more stories on the first story board are blocked by the sub-story inserted into the backlog list or implemented into the second story board for the second team.
3 . The system of claim 2 wherein the sub-story in the backlog list or on the second story board displays a blocking icon to indicate that the sub-story is blocking the at least one story.
4 . The system of claim 3 wherein the at least one story displays the blocking icon to indicate that the at least one story is blocked by the sub-story.
5 . The system of claim 4 wherein, responsive to completion of the sub-story, the blocking icon is removed from the story and the sub-story, and the story displays a priority icon indicating a priority of the story.
6 . The system of claim 1 wherein the one or more story board control panels comprise a story creation and editing control panel.
7 . The system of claim 6 wherein the sub-story is created using a sub-story tab within the story creation and editing control panel.
8 . The system of claim 1 wherein the one or more story board control panels comprise a sub-story creation and editing control panel.
9 . The system of claim 8 further comprising a selection of an expedite class of service or a fixed date class of service received from the sub-story creation and editing control panel.
10 . The system of claim 1 wherein each of the one or more stories associated with the sub-story displays a sub-story icon.
11 . The system of claim 10 wherein, responsive to clicking the sub-story icon, content for a sub-story tab, comprising details about the sub-story, is displayed on a story creation and editing control panel.
12 . The system of claim 11 wherein the content for the sub-story tab comprises the owner, title, delivery date and progress of the sub-story.
13 . The system of claim 12 further comprising the content for the sub-story tab updated to reflect the progress of the sub-story, responsive to the second team moving the sub-story through the second story board.
14 . The system of claim 1 wherein the sub-story displays a parent story icon in the backlog list or on the second story board.
15 . The system of claim 14 wherein details about the at least one story associated with the sub-story are displayed, responsive to hovering a mouse over the parent story icon, wherein the details comprise a story ID, an owner, a title, the first team requesting the sub-story and a priority.
16 . The system of claim 1 wherein the first team and the second team communicate with one another via a comments tab in the story creation and editing control panel.
17 . The system of claim 1 wherein the first team deletes the sub-story only if no progress on the sub-story has been made by the second team.
18 . The system of claim 1 wherein at least one of the one or more stories on the first story board is marked complete only if the sub-story is complete.
19 . The system of claim 1 wherein the first team and the second team are the same and wherein the sub-story comprises a milestone to be achieved by the first team.
20 . A system, comprising:
a) a project management software hosted on one or more server computers communicatively coupled to a network;
b) a story board within the project management software comprising one or more stories for a first team; and
c) one or more first story board control panels within the project management software configured to create a sub-story to be inserted into a second story board comprising one or more stories about, but not used by, a second team, wherein the first team is responsible for updating the one or more stories to move the one or more stories, including the sub-story, through the second story board.