Skip to content
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

Jump to bottom

Fix url #23

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

Fix url #23

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
2 changes: 1 addition & 1 deletion data/module-2/part-5/framework.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -346,7 +346,7 @@ hours and money into securing the features?
Securing a feature post-release is almost always more cumbersome than securing
the feature during the development process. This "cumbersomeness" or cost can
be compared to bugs and the need of fixing them, see e.g. [the true cost of a
software bug](http://blog.celerity.com/the-true-cost-of-a-software-bug).
software bug](http://celerity.com/the-true-cost-of-a-software-bug).

Moreover, it is challenging to estimate which features are such that will
remain in the software and which ones will not. Whilst the goal of agile
Expand Down