Time for another (almost) weekly installment of Interesting Post. Every week I feel like the number of agile related articles was pretty light… but then I go to build this post… and realize there was a ton of great content out there. I guess I ju…
Uncategorized
Amp, Architecture, Avalanche, Business Agility, Contracts, Document Templates, Dynamism, One Thing, Principle, Proceedings, Project Failure, Quote Of The Day, Related Articles, Retrospective, Scope, Scrum, Sprint, Stasis, Team Members, Time Budget
Traditional software development teams are supposed to work within the confines of the software ‘Iron triangle’. The three sides of the triangle are Scope, Schedule and Cost. Since Agile places a lot of emphasis on quality, it is often considered a dimension which sits at the middle of the triangle. For any project to succeed there is a need to maneuver one of the dimensions keeping the others relatively constant. Most Agile teams vary the scope and keep a tab on Cost, Schedule and Quality. Jim Highsmith suggested that the Iron triangle, imposes a lot of constraints on the flexibility of the Agile teams and suggested an alternate Agile Triangle. [Learn more][1].
[1]: http://www.infoq.com/news/2009/08/agile-triangle
Uncategorized
Agile Software, Confines, Constraints, Flexibility, Infoq, Iron Triangle, Jim Highsmith, Lot, Scope, Software Development Teams, Traditional Software Development
Last week I did a post called “The Hard Reality”. I made the point that anything you build… any document you create… that doesn’t result in revenue for the business… is wasting time and money. Personally, unless you build software as a hobby……
Uncategorized
Absolute, Great Software, High Quality Software, Making Money, People, Performance Time, Prerequisite, Quality Constraints, Quality Performance, Sake, Scope, Selling Software, Software Metrics, Software Teams, Time And Money, Time To Market, value, velocity, Wasting Time
I don’t want to be a Scrum guy. I don’t want to be an XP guy. I don’t want to be a Lean guy… or a Kanban guy… or a DSDM guy… or a RUP guy… or a PMI guy. For that matter… I don’t even want to be an Agile guy.As my experience has broadened o…
Scrum, XP
Agile, Better Chance, Budget, Common Goal, DSDM, Extent, Human Beings, Kanban, Labels, Marketplace, Pmi, Process Implementation, RUP, Scope, Scrum, Tent, Waterfall
A rejection of the idea that agile teams should use a Release Backlog in addition to the already generally accepted Product and Sprint (or Iteration) Backlogs.
Uncategorized
agile release planning, Backlog, Backlogs, Contracts, Conventional Product, Conversations, Estimating and planning, Guarantee, High Priority, Horizon, Iteration, Literature, Preference, product backlog, Release Planning, Scope, Sprint, sprint backlog, Stakeholders, Subset, Top Priority, velocity, Velocity Changes