-
Notifications
You must be signed in to change notification settings - Fork 1
/
README
83 lines (66 loc) · 3.31 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
Overview
========
The basis of this app is to have a blank canvas (the main page), that the
users can place planning cards onto for various purposes, including:
- Brainstorming
- Agile and Kanban development
- Organizing tasks and ideas
- Lean Coffee style dstributed meetings
JS will cover most of the heavy lifting for the AJAX side of things.
Depending on how the server handles the load initially, we might have
to steal some code from Etherpad for the collaboration piece.
Main Functions
==============
On initial load, the user will be presented with a login window. After
inital login or registration the user will be automatically forwarded
to the board.
The board will have a button to create a card. This will show a card
over top of the board with two editable fields, the summary and the
user story. At the bottom of the card, there will be three buttons 'Save',
'Cancel' and 'Flip'. Once card has been flipped a user can update the
acceptance criteria.
Once a card has been placed on the board, the user can then click and
drag the card to anywhere on the board. Cards should be able to be
stacked and organized into piles (probably needs some custom
functionality for that).
It would also be nice to have columns for cards to travel through, ala Kanban
or Trello.
Multiple users should be able to create and edit cards at the same time.
Have to figure out how to handle conflicts upon edit.
Cards will be stored in a SQLite database. Eventually we would want this
mapped to some form of DCVS (git or mercurial).
Estimates should be collaborative. Not sure if this needs to be a js
function or a backend function, but having everyone on the board vote
for a story point estimate would make the process easy.
Because of this, there probably needs to be some form of notification
function for users that are logged in that someone else is viewing
and editing the card.
Multiple boards for different projects. Cards should be distinct to a
board, but you should be able to migrate them to a new board.
Potential Additions
===================
Should interface with Jira, TFS and whatnot. This could be a useful
interface for planning sessions - especially if it created the right
tickets in whatever system they used. This would probably have to be a
separate application (though we could call it through the app once it
was working).
Some form of tracking cards as they're completed would be nice (supposing
people wanted to use the app for that). But that's very much out of scope
at this point.
OAuth login for in-promptu planning sessions. Be able to create a new board
with a secret key to pass around and route people to the correct board. Then
the server could be a public facing application for use at conferences and
classes on the Agile method.
User Stories/Scenario Examples
==============================
- Creating a new card
- As a user, I want to create a new card. I want to input in what goes on
the card and place it on the board through a RESTful JSON interface.
- As a user, I want to click a button and have a blank card appear on the
left hand side with a field for me to add information.
- As a developer, I want to automatically create cards based on outside
events, such as an RSS feed.
- Changing a card
- Moving a card
- Finishing a card
- Replaying changes made to cards