Skip to content

managing requirments is part of good design. They should be merged as it... #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tomsquires wants to merge 1 commit into
base: master
Choose a base branch
from
Open

managing requirments is part of good design. They should be merged as it... #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions README.textile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,18 +85,12 @@ h2. General
** Fix it if it ain't broke
*** We only refactor code that we are actively working on, otherwise we live with the imperfections and tackle higher priority issues.

h2. Requirements

* DO
** Ensure that acceptance criteria are clearly identified before starting work on a story
* CONSIDER
* AVOID
* DON'T

h2. Design

* DO
** Follow SOLID:http://en.wikipedia.org/wiki/SOLID_(object-oriented_design) design principles
** Ensure that acceptance criteria are clearly identified before starting work on a story
* CONSIDER
** Pursuing a functional approach - immutable types, "pure functions":http://en.wikipedia.org/wiki/Pure_function etc
** Asking for a design review at any point of working on a story
Expand Down