Agile Terminology


Terminology:

->Agile: This is described in other sections

->User stories: The “old school” Requirements are converted into well defined statement and also with relevant test cases/blue-print.

Example: DELL “build’s computer’s”, so that the customer can use utilize for personals or office use. This will also help DELL to build it’s revenues, by seeling it.

The making /creation of product work schedule will defined in terms of how many user stories for the specific time period are produced

->“Testable” part is also mentioned in the “user story”
->The component or module design/development teams or test teams will concentrate on particular “user story”

->Planning Game: This is time based event where “user stories” are confirmed , prioritized and planned . This is part of
XP [Kent Beck’s: Extreme programming model

•Daily stand-up/SCRUM call:

This is derived from the one of the “Agile” model.

->The SCRUM process says it is 15 minute daily call to discuss about the issues and concerns.
->And the teams will take-away the problem statement/issue will discuss with further between affected parties and will report into the “next call” or discuss by e-mails, group meetings and phone calls.
-> This is kind of get-togher to understand who is working on what, what need to be done to resolved the problem

•Rolling Plan
->Entire team should meet periodically for review of the recent activities. At the end of the “meeting”, the following should come out:

•What worked well?
•Lessons learned
•What to do next time differently
•What Puzzles us?

Workshop->

->SCRUM has pre-defined process of schedule/quarterly/bi-weekly/quarterly
->This is more of quarterly/fixed schedule based get-together of key-stake-holders [Product, customers, Developers, program Manager, Delivery managers] in specific project,product and Program.
->The “User stories” or High lever project issues, planning may be the key components for this discussions
->Here “retrospective” is done, that means analyzing what went wrong?, What went right [really], and take-away for the next “project implementation”
->Here we also discuss the potential issues with whole project and programs and a this organized by delivery organization.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s