Search results

Jump to navigation Jump to search
  • ...gileforall.com/2015/09/does-your-culture-require-your-demise-pig-chicken-3-agile-safari/ |site=Agile For All
    558 bytes (58 words) - 07:52, 4 September 2015
  • ...|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
  • |goal=quickly have a team take an agile quantum leap |theme=Agile, Maneuver, Team
    3 KB (451 words) - 10:10, 9 March 2014
  • ...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
  • ...team; Context to help select the right combination of agile methodologies for this particular team at this particular time.
    328 bytes (54 words) - 19:24, 9 May 2013
  • *is essential for all learning (on all levels: group and {{p|tribe}}); *encourages high levels of interpersonal risk taking, such as {{p|ask for help}} and {{p|temperature reading}}; and
    2 KB (270 words) - 10:51, 23 December 2013
  • |theme=Agile, Scrum ...nterface. Based on the {{p|agile manifesto}} and {{p|principles behind the agile manifesto}}, both parties may agree on the following ‘rights’ up front.
    3 KB (516 words) - 09:31, 16 June 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
  • |goal=spread all knowledge while being productive and collectively own the product |theme=Agile, Lean, Extreme Programming
    1 KB (223 words) - 13:32, 9 June 2016
  • |theme=Agile, Scrum |so=Slow down to speed up—create some slack time for process improvement by pulling in just a bit less than yesterday's weather.
    1 KB (213 words) - 14:37, 12 July 2013
  • *Organize Training for Everyone. *Opt for One Week Sprints.
    1 KB (154 words) - 18:33, 6 January 2014
  • {{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
  • |theme=Agile, Lean, Scrum, Kanban *Provides easy access to all stakeholders.
    1 KB (199 words) - 13:41, 22 October 2014
  • |background=See [[agreement]] for its definition. ...her with the {{p|agile dojo}} becomes '''instant culture''', or '''instant agile culture''' (or lean if that is your flavor); intentional culture of [[agree
    3 KB (434 words) - 10:52, 20 April 2014
  • ...owner}}, the {{p|flow master}} (or ‘flow owner’ or ‘flowner’) and the {{p|agile coach}}. ...e enough and actively blocks the increasingly agitated attempts by the {{p|agile coach}} to help the {{p|squad}} help themselves?
    5 KB (677 words) - 05:41, 28 September 2016
  • |theme=Agile ...bove a certain threshold, minimize the items lead time, and follow any and all changes in the spec while the item is in progress.
    2 KB (385 words) - 09:56, 16 May 2014
  • |theme=Agile, Lean, Scrum, Product ...a concise and relevant template and use it consistently and repeatedly in all your communication.
    1 KB (184 words) - 13:31, 16 June 2014
  • Goal: To find out which projects can and cannot be picked up with agile/lean. #Ask participants to generate an exhaustive list of all current and upcoming projects; one project per note.
    4 KB (472 words) - 07:40, 3 September 2015
  • |goal=secure the essential ingredients for a successful agile engagement |theme=Agile, Kanban
    4 KB (608 words) - 14:40, 22 November 2018
  • |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 |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
  • |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
  • |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
  • |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
  • |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
  • 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
  • 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
  • |theme=Agile, Lean, Scrum *Becoming dependent on single specialists is all too easy.
    1 KB (236 words) - 19:39, 26 May 2013
  • 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
  • |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
  • |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
  • ...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
  • |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
  • {{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
  • |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
  • |theme=Agile, Lean, Quality *''done'' for upstream equals ''ready'' for downstream
    3 KB (448 words) - 14:03, 19 July 2019
  • 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
  • |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
  • 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
  • #Scope—total feature set or all functionality that needs to be delivered; all functional requirements; please note that everything required is different #Time—the moment in time when it needs to be ready for use;
    6 KB (1,046 words) - 09:32, 2 August 2013
  • |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
  • |context=anytime for a {{p|squad}} or {{p|tribe}} chipping away at a collective endeavor, and es ...st to you, but also because it is a [[leading indicator]], which makes you agile. Most financial metrics are [[lagging indicators]], making it hard to react
    5 KB (757 words) - 17:37, 8 May 2014
  • {{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
  • |theme=Agile, Scrum {{tag|Agile}}
    15 KB (2,410 words) - 06:47, 19 October 2015
  • ...he Deming Wheel (PDCA Cycle) and the need to focus on management processes for continuous improvement, including both '''Breakthrough Management''' and Da {{p|hoshin kanri}} is an organising framework for strategic management. It is concerned with four primary tasks:
    5 KB (783 words) - 13:17, 22 October 2018
  • |theme=Agile, Lean, Jumpstart, Don’t just do something ...ises, overdeliver and treat every commitment as though it's an opportunity for a transformation, the only way you can do this is to '''turn down most oppo
    5 KB (738 words) - 14:21, 9 July 2018
  • How {{organization|Jimdo}} scales their agile organization to 180 people (which is beyond {{p|dunbar’s number}}. *{{p|life is a broccoli}} to embed {{p|purpose, principles, practices}} at all levels of the {{p|chaorganization}}.
    6 KB (876 words) - 15:32, 27 April 2014
  • |theme=Agile, Scrum See below for a detailed example of a {{dor}}.
    7 KB (1,220 words) - 06:58, 10 August 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

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