Skip to main content

Home/ Agilesparks/ Group items tagged product-ownership-101-list

Rss Feed Group items tagged

Yuval Yeret

James Shore: The Art of Agile Development: Stories - 0 views

  • "Non-Functional" Stories AllyPerformance OptimizationPerformance, scalability, and stability—so-called non-functional requirements—should be scheduled with stories too. Be sure that these stories have precise completion criteria. See Performance Optimization for more.
  • Spike Stories AllySpike SolutionsSometimes programmers won't be able to estimate a story because they don't know enough about the technology required to implement the story. In this case, create a story to research that technology. An example of a research story is "Figure out how to estimate 'Send HTML' story". Programmers will often use a spike solution (see Spike Solutions) to research the technology, so these sorts of stories are often called spike stories.
Yuval Yeret

InfoQ article: "Pulling Power: A New Software Lifespan" - 0 views

  • how Kanban metaphor from Lean manufacturing and the Feature Injection template play into Behaviour Driven Development, working together to help us identify the most important software, reduce unnecessary artifacts at each stage of development, and produce the minimum necessary to achieve a vision
  • The artifacts signal each role to create further artifacts until the vision is implemented and the business value is earned
  • "Generating reports," he says, "is like lead. It's easy to work with, and it's cheap. It's also heavy, worthless, and drags you down. Developers sink a lot of time into writing report software. Why? Buy it, install it, hack it so it works. Use Excel. Don't spend money writing report software, unless you're the kind of company that sells them to other companies.
1 - 18 of 18
Showing 20 items per page