Skip to main content

Rabbit, Horse and Elephant approaches

Rabbit—small, fast, and brief-lived. Rabbit tasks are generally smaller initiatives with shorter lifetimes, where near stakeholder participation is possible. Rabbit projects typically encompass a lesser number of stakeholders. Rabbit projects do not spend an excellent deal of time writing the necessities, but use conversations with the stakeholders as a manner to difficult the requirements written on tale playing cards. Rabbit tasks nearly constantly collocate the business know-how stakeholders with the enterprise analysts and the developers.

Horse tasks are possibly the maximum not unusual corporate projects—they may be the “midway house” of formality. Horse initiatives need some formality—it's miles probable that there's a want for written necessities in order that they can be surpassed from one branch to some other. Horse initiatives have medium durability and contain more than a dozen stakeholders, regularly in several locations, elements that necessitate continuously written documentation.

Elephant—stable, strong, lengthy life, and a long reminiscence. An elephant venture has a need for a whole necessities specification. in case you are outsourcing the paintings, or in case your organizational shape requires whole, written specifications, you’re an elephant. In positive industries, including pharmaceuticals, aircraft manufacturer, or the army, regulators demand not most effective that full specs be produced, but added that the procedure used to produce them be documented and auditable. Elephant initiatives typically have a protracted duration, and that they involve many stakeholders in distributed places. There also are a big quantity of builders, necessitating greater formal ways of speaking

Aziz

Comments

  1. UnknownOctober 31, 2018 at 12:33 PM

    Some points to consider:

    1. In the Rabbit approach - Usually the requirements are not written due to the short time they have to have the project done. Basically you gather the requirements and act altogether: sponsors, business analysts and developers. There is no time and/or money to spend too much time discussing about the requirements.

    2. In the Elephant approach - This is the opposite! This is too solid. When you want to implement a change it's like a transatlantic turn, that's too slow because the process is too long.

    ReplyDelete

Post a Comment

Popular posts from this blog

The Brown Cow Model

This model of work has four views of work which are What, Now, How and Future. The two horizontal and the vertical axes separate What from How, and Now from the Future. The Brown Cow Model illustrates four points of view that help to uncover the real business problem and identify useful innovations. The four quadrants which are - What-Now, What-Future, How-Now, and How-Future show the different viewpoints of work. Generally, it is not sufficient to have only two views of business - the "as is" and the "to be". To get a true light on the business problem and to ensure innovations, more views are necessary. Aziz
3 comments
Read more

The Brown Cow Model in Agile

There are reports stating, “agile does not help in innovation”. As there is a pressure to develop anything, they can produce within the time allowed. The greatest pressure is for maintaining the speed of the project, not for its innovative solutions. When we talk about innovation it means new thinking. We do not mean that innovation is invention. Innovation is different thinking about the business problem with the intention of finding beneficial solutions. User stories that are not based on real business stories will always have a hard time being innovative. Without some innovative thinking, it is very easy to propose only that you increment something and let it go through it. When a BA investigates a business history, this professional needs to be purposely trying to encourage innovation. The Brown Cow Model illustrates the ability to analyze the same business history from several different points of view. From there, innovations are discovered t
Post a Comment
Read more

Usability Requirements

Usability Requirements Ease of Use Requirements: This requirement deals with the aspect to make the product usable for the user. The product should have the following properties for the ease of use Efficiency of Use  Ease of remembering    Overall satisfaction Feedback Personalization and Internationizational Requirements: These requirements deal with the way the product can be changed or advanced related to the user's choices or preferences. The product could have the following personalized requirements: Language or spelling preferences Currency choices Personal Configuration options Learning Requirements: These consider how easy it is to learn to use the product or the service. These requirements may differ on the level of technology or any advancement involved in the product. Some services also require for the engineers or the user to train in a specific program to be able to efficiently use the service or the product. Understandability and Politeness Requiremen
Post a Comment
Read more