Other Heavy Weight Methodologies
Standards and Definitions
Body of Knowledge
Sometimes, heavy weight methodologies work, but
there are extensive costs, and the risk in using them
in dynamic environments is high.
It takes common sense practises to extreme levels - “turning the
dials to 11!”
• If code reviews are good, review code all the time (Pair
• If testing is good, everybody will test all the time (Unit Testing)
• If design is good, make it part of everyone’s daily business
• If simplicity is good, always leave the system with the simplest
design that supports it’s current functionality.
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
Processes and Tools
Following a Plan
That is, while there is value on the right, we value the items on the left more.
Our highest priority is to satisfy the customer
through early and continuous delivery of
Welcome changing requirements, even late in
development. Agile processes harness change for
customer's competitive advantage.
Working software is the primary
measure of progress.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers
Build projects around motivated individuals.
Give them the environment and support they
need, and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
and good design enhances agility.
Continuous attention to
together daily throughout the project.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
team reflects on how
to become more effective, then tunes and adjusts
At regular intervals, the
its behavior accordingly.
Working software showcased to
business, tested with customers
Story = Light weight piece of requirement
As an Online Banking User
I want to link my Loan Account with my existing Saving Account
So that I can view all my Accounts at one place
2 story points
<Actor> <action><by |to |for |of > <a(n) object> <the result>
• Display Customer’s Account
• Allow Customer to select and link the Account
• Validation on Customer Account data
• Display all Linked Accounts under “My Accounts” page