Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this:

Typical Software Development Life-cycle explained

Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development.

"A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives."

Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a script or stories to actors to act in the dialog delivery with lights, camera and action that's called a TAKE.

On the very same lines we have User Stories which can be a powerful tool to be converted into a Use-case scenarios. User Stories can be categorized into user needs, wants and demands from usability perspective of the system development.

Definitely Use cases are key building blocks of any software development life cycle which is again powered by user stories. It is well known fact, mislead requirement will lead to many gaps created in early part of project to be rectified at each cycle of the project in later phases of the project.

Use Cases: Requirements in Context (2nd Edition)

User Stories Applied: For Agile Software Development

Comments

Porter's outside-in and Hammel - Prahald's Inside-out

Over the years inspiration and motivation to out do something which creates spark in the genre of concurrent times is always been challenge for all of us, to make things happen requires a plan, an out of the box solution to rationalize its existence. More often than not inspiration are unknown to us, which may leads to different scenarios of multiple ways of looking at things differently and indifferently also, anyways there are always n-1 degrees of freedom to think differently for n+1 different ways looking at things. Inspired by a spiral which is coincidentally a galaxy in our spatial system gives us views like --if one start from a point from outer end to reach at center, will reach from outside-in and if one starts from the center and circle outwards move than that will be inside-out thinking. So again its up to individuals, which way move. Traveling by we see stars and other objects binding each other with gravitational forces. Galaxy One of the many management stra

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis

Frisking out project risk

Risk Management road sign (Photo credit: Wikipedia ) So what is a risk ? First understands and identify a risk is most important part of risk management.A risk is a probability of uncertainty associated with executing certain item/task/process/work etc. A risk generates out as soon as we initiates a task. A critical resource in terms of skill set, in a team is a potential risk of leaving the project in between because of unavoidable reasons. So a risk is inevitable, only thing we can do is ; manage and mitigate. Just like handling/catching error in software program . Always plan for the element of risk in project from the start and reiterate control over it for any contingencies. Steps to assess risk: Identify---------->Analyze--------------> Set priority to each risk Steps to control risk: Mitigate------------>Plan for contingency----------> Quantify it and Set a control process Design a Solution process at the team level: Taking help of the experts inv

Project Portfolio-Program Management

Search This Blog