Search results

Jump to: navigation, search
  • ...|boom buffer}}. Everyone, including the {{p|product owner}} is very happy, for now the {{p|development team}} can work focused and is not disturbed by ext ==Generated List of all Pearls==
    1 KB (189 words) - 16:13, 22 March 2014
  • |theme=Agile |context=in a large organization, {{p|scrum}} initiatives are popping up all over the place—it's catching on like wildfire and an {{p|early majority}}
    3 KB (448 words) - 17:29, 26 May 2013
  • |theme=Agile, Scrum See below for a detailed example of a {{dor}}.
    7 KB (1,220 words) - 06:58, 10 August 2016
  • |theme=Agile, Lean, Quality *''done'' for upstream equals ''ready'' for downstream
    3 KB (448 words) - 14:03, 19 July 2019
  • |theme=Agile, Scrum |wish=You want to know when items are done, ready for the next step.
    3 KB (422 words) - 13:35, 26 May 2013
  • |goal=test for clear, elegant, and intelligible requirements |theme=Agile, Scrum
    2 KB (268 words) - 13:14, 26 May 2013
  • ...cel in providing the best solution, sustain top performance, and have hun, all at the same time |theme=Agile, Lean, Scrum, Team
    586 bytes (90 words) - 10:08, 9 March 2014
  • |theme=Agile, Lean, Scrum *Becoming dependent on single specialists is all too easy.
    1 KB (236 words) - 19:39, 26 May 2013
  • |theme=Agile, Scrum |context=product development in an agile context, e.g. using {{p|scrum}} or {{p|kanban}}.
    1 KB (239 words) - 10:18, 16 June 2013
  • |theme=Agile |context=tough situations with a need for difficult or complex decision making.
    3 KB (409 words) - 10:27, 18 July 2016
  • |theme=Agile, Scrum, Product When the work is simply too much for a single {{p|product owner}}, split it up between a {{p|strategic product o
    15 KB (2,380 words) - 08:05, 11 June 2019
  • |theme=Agile, Lean, Scrum, Product ...story includes providing the capability and maintaining a healthy codebase for future work.|Martin Fowler}}
    10 KB (1,523 words) - 05:22, 2 July 2019
  • |theme=Agile, Lean, Kanban |so=Institutionalize reflection and retrospection at all levels and across all disciplines.
    15 KB (2,242 words) - 17:14, 19 November 2017
  • {{tag|agile}} ...ed to have but won't have this time". So there ''is'' an explicit category for what you are ''not'' going to require.
    3 KB (456 words) - 10:01, 25 December 2013
  • {{tag|agile}} ...he effort of getting it up-to-date; e.g. architecture documents can linger for a while
    929 bytes (136 words) - 16:29, 11 February 2012
  • {{tag|agile}} ...tes, the cycle time for the batch is five minutes. However, the cycle time for an individual part is 13.6 seconds (5 minutes x 60 seconds = 300 seconds, d
    8 KB (1,273 words) - 09:51, 23 February 2014
  • Without a structured and centralized approach for managing an organization’s knowledge, one or more of the following issues *It is not clear whether all the company knowledge is overall consistent.
    8 KB (1,225 words) - 16:13, 21 October 2014
  • |theme=Agile |so=Conduct a small and focused workshop that brings out the best in all.
    2 KB (316 words) - 13:37, 20 June 2014
  • |theme=Agile, Lean, Scrum |wish=Overview and clear strategic goals aligns forces and eases planning on all levels.
    12 KB (1,746 words) - 13:48, 22 October 2014
  • |theme=Agile ...of 1, 2, 3 or 4 weeks each. This leaves room of ‘one week out of time’ for a release review, retrospective and planning.
    5 KB (774 words) - 21:13, 20 February 2014

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