Search results
Jump to navigation
Jump to search
- |site=Good Requirements2 KB (172 words) - 11:42, 15 August 2016
- ...nd tasks that are completely done. Increase the amount of work if emergent requirements or other insights tell you so. ...p|ready to release}}. You want to interpret the {{p|burn-down chart}} as a good portrayal of estimated remaining effort, and to use that portrayal to devel2 KB (280 words) - 09:17, 9 April 2013
- ...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
- #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
- **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
- ...formal language to do so. Remember, the goal of a {{p|story}} is to have a good conversation ...can be items that are added while in a hurry. The need to be rewritten as good stories later to get them {{p|ready to build}}, but were initially just tos10 KB (1,523 words) - 05:22, 2 July 2019
- *Have updates of the schedule, good or bad, as soon as the information is available. *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
- *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; and7 KB (1,220 words) - 06:58, 10 August 2016
- As with all good teams, everyone is !rst accountable for the teams gear, followed by their t ...ams||Jon Katzenbach, Douglas Smith}} identifies six basic requirements for good teamwork:6 KB (784 words) - 12:58, 2 August 2016
- |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
- ...ppen. The same thing is true of change. Beck and Cowan have identified six requirements that must be met in order for change to occur – all of them must be prese ...perspective, not the least of which are education, meditation, travel, and good therapy.10 KB (1,655 words) - 17:06, 23 November 2018
- #How much good for this metric is enough or too much, what signs do we look for? {{quote|The purpose of measurements is to motivate the parts to do what is good for the organization as a whole.|Eli Goldratt}}16 KB (2,430 words) - 08:03, 4 August 2020
- :…initial requirements are often far from perfect and change constantly and may not cover every ne :…perfect is the enemy of good enough.There are times later in development where you can determine detaile15 KB (2,380 words) - 08:05, 11 June 2019