Search results

Page title matches

• Requirements game
  [[File:Requirements Game.png|right|thumb|link=http://pearllanguage.org/images/f/f2/Requirements ...Explain that this is their canvas and that they need to implement as many requirements they receive from the analysts as possible.
  3 KB (541 words) - 09:32, 28 March 2015
• Non-functional requirements
  ...id Ameller, Claudia Ayala, Jordi Cabot, Xavier Franch|title=Non-functional Requirements in Architectural Decision Making}}
  294 bytes (31 words) - 09:22, 18 January 2014

Page text matches

• Non-functional requirements
  ...id Ameller, Claudia Ayala, Jordi Cabot, Xavier Franch|title=Non-functional Requirements in Architectural Decision Making}}
  294 bytes (31 words) - 09:22, 18 January 2014
• Ambiguity test
  |goal=test for clear, elegant, and intelligible requirements |context=preparing {{pbi}}s and other forms of requirements and specifications.
  2 KB (268 words) - 13:14, 26 May 2013
• Planguage
  ...|Tom Gilb}} and [[author|Kai Gilb]]'s {{p|planguage}} allow you to express requirements is a precise, concise, coherent and complete way.
  251 bytes (37 words) - 11:19, 6 September 2019
• Requirements game
  [[File:Requirements Game.png|right|thumb|link=http://pearllanguage.org/images/f/f2/Requirements ...Explain that this is their canvas and that they need to implement as many requirements they receive from the analysts as possible.
  3 KB (541 words) - 09:32, 28 March 2015
• Track done
  ...nd tasks that are completely done. Increase the amount of work if emergent requirements or other insights tell you so. ...reasing the amount of known work if the task grows in size due to emergent requirements or other insights gained during the Sprint.
  2 KB (280 words) - 09:17, 9 April 2013
• Agile business analyst
  ...A), successfully managing an agile product development depends on defining requirements in smaller increments and '''working more collaboratively with the {{p|deve ...alysts are conditioned to believe that they can and should define detailed requirements at the beginning of a project.
  9 KB (1,280 words) - 13:07, 26 September 2012
• Scale specification
  #The Principle of ‘'''Scales should control the Stakeholder Requirements'''’ ...easure that give you the most direct control over the critical stakeholder requirements. Chose the Scales that lead to useful results.
  3 KB (498 words) - 07:50, 4 April 2013
• Behavior-driven development
  |site=Good Requirements
  2 KB (172 words) - 11:42, 15 August 2016
• Test-driven development
  *can be used to specify detailed requirements on a just-in-time (JIT) basis throughout construction—writing the accepta
  1 KB (151 words) - 10:52, 10 August 2016
• Similarity feeds predictability
  **resource requirements; Similarity in the size of requirements reduces the amount of effort expended on analysis, design, coding, testing,
  3 KB (407 words) - 11:20, 18 March 2014
• Gilb’s 10 Agile Principles
  #Change the requirements, based on quantified value, cost experience, and new inputs.
  1 KB (205 words) - 14:29, 18 October 2013
• Cruise missile
  ...nsuring that it passes all tests and is {{p|ready to ship}}, even when the requirements and specifications change while the item is in progress. That is, how can y
  2 KB (385 words) - 09:56, 16 May 2014
• Andon cord
  ...that you cannot complete the product successfully in time due to emergent requirements, technical problems, quality issues, or the loss of critical people or capa
  2 KB (348 words) - 07:23, 13 September 2018
• Golden triangle
  ...eature set or all functionality that needs to be delivered; all functional requirements; please note that everything required is different from what is actually ne ...lity, maintainability, security, performance, …; in fact al non-functional requirements.
  6 KB (1,046 words) - 09:32, 2 August 2013
• Definition of done
  *non-functional requirements are met;
  3 KB (422 words) - 13:35, 26 May 2013
• MoSCoW
  {{tag|requirements}}
  3 KB (456 words) - 10:01, 25 December 2013
• User story
  ...://www.mountaingoatsoftware.com/articles/27-advantages-of-user-stories-for-requirements |title=Advantages of User Stories for Requirements
  10 KB (1,523 words) - 05:22, 2 July 2019
• Reciprocal altruism
  *Always know what needs to be produced with clear requirements, and {{p|crystal clear acceptance criteria}}.
  3 KB (516 words) - 09:31, 16 June 2013
• Ready to build
  *The right level of detail in requirements, both functional and qualitative increases the immediately actionability of *how it will be implemented, meeting or exceeding the non-functional requirements and within the technological and architectural guidelines; and
  7 KB (1,220 words) - 06:58, 10 August 2016
• Agile architect
  |wish=The best architectures, requirements, and designs emerge from self-organizing teams. |wish full=The best architectures, requirements, and designs emerge from self-organizing teams.
  15 KB (2,410 words) - 06:47, 19 October 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)