Search results

Jump to navigation Jump to search
Results 1 – 18 of 18
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  • |theme=Agile, Scrum ..., and makes everybody happy and avoids surprises. Tweaking and tuning your product based on feedback and {{p|measurable goals}} keeps everyone happy.
    4 KB (523 words) - 20:45, 18 March 2016
  • |theme=Agile, Lean, Scrum |so=Have the product owner crew decide which build squad will pull this item into their sprint b
    3 KB (565 words) - 08:59, 16 June 2013
  • |goal=evolve your product as stacked layers of quality |theme=Agile, Lean, Quality
    3 KB (448 words) - 14:03, 19 July 2019
  • {{tag|product}} *Reiterate the Product Vision, Measurable Product Goals and output
    5 KB (639 words) - 10:29, 1 February 2017
  • Adopting agile practices for mission critical systems, creating a “insurance policy”: *order the {{p|product backlog}}:
    3 KB (490 words) - 14:02, 12 July 2013
  • |theme=Agile, Scrum |context=creating and evolving a product while embracing change.
    15 KB (2,410 words) - 06:47, 19 October 2015
  • 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
  • ...am describes what information is recorded about some entity, for example a product and which business rules apply to this entity. ==Conceptual schema design==
    8 KB (1,225 words) - 16:13, 21 October 2014
  • |theme=Agile ...ship}}, that is, tested and accepted according to functional and technical design.
    2 KB (385 words) - 09:56, 16 May 2014
  • |theme=Agile, Scrum, Product {{tag|product owner}}
    15 KB (2,380 words) - 08:05, 11 June 2019
  • |theme=Agile, Lean, Scrum, Product ...do with your product. The nouns are the objects or parts that make up your product.
    10 KB (1,523 words) - 05:22, 2 July 2019
  • A {{p|piecemeal growth story}} about agile transfomation of an organization no larger than [http://en.wikipedia.org/wi ...organization relies on the concept of piecemeal growth. Rather than try to design the overall structure to be used, we are working with smaller segments of t
    6 KB (953 words) - 08:01, 11 June 2013
  • |goal=invest most of your time efficiently building, implementing the product |theme=Agile, Scrum
    7 KB (1,220 words) - 06:58, 10 August 2016
  • {{tag|agile}} How often a part or product is completed by a process, as timed by observation. This time includes oper
    8 KB (1,273 words) - 09:51, 23 February 2014
  • *downloading the product; *login into the product;
    16 KB (2,430 words) - 08:03, 4 August 2020
  • |theme=Agile, Scrum, Team ...structures and patterns based on its own internal dynamics. Organization design is not imposed from above or outside; it emerges from the interactions of t
    11 KB (1,487 words) - 20:02, 30 May 2016
  • |context=As a team develops the product, bugs are invariably detected. The usual tendency is to write bug reports a ...xisting bugs should be prioritized by the Product Owner and managed in the Product Backlog. Bugs appearing from outside the sprint such as customer emergencie
    12 KB (2,011 words) - 14:32, 12 July 2013
  • |theme=Agile, Lean, Kanban ...ide-design-for-developers/|person=Zach Holman|site=Zach Holman|title=Slide Design for Developers}}
    15 KB (2,242 words) - 17:14, 19 November 2017