Search results

• Definition of done
  |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
• Ambiguity test
  |goal=test for clear, elegant, and intelligible requirements |theme=Agile, Scrum
  2 KB (268 words) - 13:14, 26 May 2013
• Blocker waiting room
  |theme=Agile, Scrum, Kanban ...g while waiting on external events and keeping a clear visual oversight on all work in progress minimizes waste and stale items, keeps things flowing, and
  3 KB (446 words) - 13:03, 26 May 2013
• Sprint goal
  |theme=Agile, Scrum |so=Set a clear goal for every sprint and only pull in work that helps reach that goal.
  4 KB (650 words) - 12:40, 7 November 2016
• Season beat
  |theme=Agile ...}}s 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
• Writers’ workshop
  |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
• ORM
  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
• Agile transformation
  A {{p|piecemeal growth story}} about agile transfomation of an organization no larger than [http://en.wikipedia.org/wi ...atterns below they will generate the organizational structures best suited for the activities they need to perform. Other patterns will help generate how
  6 KB (953 words) - 08:01, 11 June 2013
• Knowledge injection
  |theme=Agile, Lean, Scrum *Becoming dependent on single specialists is all too easy.
  1 KB (236 words) - 19:39, 26 May 2013
• Culture
  All {{verb|change}} in organizations is belief change. So, create {{p|belief st {{quote|Culture eats strategy for breakfast.}}
  3 KB (368 words) - 18:19, 10 July 2015
• Daily scrum of scrums
  |theme=Agile, Scrum *address issues then and there, since all qualified people are present; i.e., unlike the {{p|daily scrum}}, do not po
  2 KB (378 words) - 13:29, 26 May 2013
• One service deserves another
  |theme=Agile, Lean, Scrum ...o make the change. Your {{p|squad}} has made the item {{p|ready to build}} for the other {{p|squad}}.
  3 KB (565 words) - 08:59, 16 June 2013
• Liftoff
  ...me from various backgrounds, struggle to collaborate, and it is unclear if all constraints, means, and skills are met to start. ==Plan for a Successful Liftoff==
  6 KB (932 words) - 14:26, 28 November 2016
• Foreign glimpses
  |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
• Estimate
  {{quote|In preparing for [projects] I have always found that [estimates] are useless, but [estimatin Watch out for:
  5 KB (717 words) - 17:13, 19 November 2017
• Set of reference stories
  |theme=Agile, Scrum ...ain a set of baselined reference stories used by all squads as a benchmark for estimation.
  2 KB (392 words) - 10:27, 16 June 2013
• Babushka of value
  |theme=Agile, Lean, Quality *''done'' for upstream equals ''ready'' for downstream
  3 KB (448 words) - 14:03, 19 July 2019
• Agile business analyst
  Business Analysts are well positioned to become critical to the success of Agile teams. Key for the {{p|agile business analyst}} are:
  9 KB (1,280 words) - 13:07, 26 September 2012
• Don’t just do something, stand there!
  |theme=Agile, Lean |context=groups, large and small, searching for future states they want to evolve to.
  8 KB (1,166 words) - 17:19, 19 November 2017
• Stable team
  Customer delight drives profitability and gives reason for existence. ...is assures that no-one stands around waiting for the team to get ready, or for the team to clean and stow their gear after the session.
  6 KB (784 words) - 12:58, 2 August 2016

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