Skip to main content

Home/ Agilesparks/ Group items tagged tdd

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Yuval Yeret

Agile Game Development: The Project Manager Role - 0 views

www.agilegamedevelopment.com/...project-manager-role.html

agile manager

shared by Yuval Yeret on 01 Jun 09 - Cached
  • The Project Manager works with the Product Owner to insure that cost is always a consideration when evaluating the Product Backlog.
  • "Super Scrum Master"
  • Among the Project Manager's responsibilities:
    • Yuval Yeret
      Yuval Yeret on 01 Jun 09
       
      sounds like what some organizations will call "Program Manager"
  • ...6 more annotations...
  • Facilitate the Product Owner's role (backlog maintenance and meetings)
  • Tracking costs, especially for production
  • Tracking project risk
  • The Project Manager on a Scrum project has to be a Scrum expert and evangelist.
  • As each Scrum team on the project evolves their practices, the Project Manager will insure that they are continuing to work effectively with the other teams
  • One example of this would be the application of Test Driven Development and similar practices to build stability. It doesn't make sense for some teams to use TDD while others don't. The PM would have to step in and work with all the teams to insure that practices won't interfere or cancel each other out.
Yuval Yeret

Ambler - Doing RFPs the Agile way - 0 views

www.ddj.com/...218101915

agile contracts agile-contracts-list

shared by Yuval Yeret on 02 Jul 09 - Cached
  • RFPs the Agile Way -- or -- Fear and Loathing in the Procurement Department
Yuval Yeret

How Is Kanban Different From Other Approaches? « AvailAgility - 1 views

availagility.wordpress.com/...ifferent-from-other-approaches

kanban

shared by Yuval Yeret on 17 Jun 09 - Cached
  • Scrum places more emphasis on the project management practices. Kanban, places its emphasis on business and value flow practices.
  • its all the same elephant, but each approach has a different view of it. At the end of the day, its having the most appropriate elephant for any given context that is most important.
  • Kanban can be differentiated by identifying its Primary and Corollary Practices.
  • ...6 more annotations...
  • Map the Value Stream
  • Visualise the Work.
  • Limit Work in Progress.
  • A Kanban approach will explicitly limit work in progress. This is distinct from managing work in progress through the use if time-boxes
  • Establish a Cadence.
  • A Kanban team will almost certainly use Corollary Practices which may be considered Primary in another process. For example, a high performance Kanban team will inevitably use technical practices from XP, such as TDD and Continuous Integration.
1 - 9 of 9
Showing 20▼ items per page