Agile and The Iron Triangle – Don’t Forget Quality

Most all project managers are familiar with this Iron Triangle of project management. When a project comes up, one must weigh the project based on the scrop, cost, and time to market. But what ever happened to the quality? Where does this come into the equation?

Agile project managers, per Bob Galen, need to take a different approach, focusing on the scope and quality of the project.

  • Maintaining a quality focus with their team so that no feature leaves the line as undone or with known defects
  • Passionately varying scope with their business partners—while always looking to deliver a high value and minimal marketable feature

Continue reading “Agile and The Iron Triangle – Don’t Forget Quality”

[InfoGraphic] – What is a Product Owner Responsible For?

Sometimes pictures are the best way to communicate something. When we came across this diagram of a Product Owners responsibilities, we liked it a lot.
Here’s a list form.
Product Owner Responsibilities:
  • Creates the product vision
  • Grooms the product backlog
  • Plans the release
  • Collaborates with ScrumMaster and team
  • Manages the product roadmap
  • Attends the sprint meetings
  • Collaborates with stakeholders
Product Owner Artifacts:
  • Product vision
  • Product backlog
  • Release burndown
  • Product roadmap

Practice Agile, Don’t Just “Do It”

Agile software development is all about inspecting, adapting, and improving upon findings to better your ___ (fill in the blank) or business or product development. Or “being” Agile as a lifestyle is to continually improve, or Kaizen.

Yep. We get that, and so does Tom Perry, who wrote a recent article on A Call to Practice. So many organizations don’t necessarily practice Agile more than they just “do it.” Never improving upon what they’re doing. That doesn’t seem very Agile at all, now does it?

And that’s exactly Tom’s point.

“We call a lot of things practices and what we really mean is “things we do”. We don’t really practice them… my call to action: find the practice in what you do. Engage in real practice with thoughtful deliberation. Find the techniques that we can all practice… to become the very best at what we do.” – Tom Perry

Continue reading “Practice Agile, Don’t Just “Do It””

2010 Agile Survey from Scott W. Ambler – Interesting Facts

AgileStateOfArt201011

Thanks to Scott. W. Ambler who put out a recent survey on Agile practices. There seemed to be enough respondents so a robust set of metrics could be pulled from the survey.

A couple interesting facts here:

  • Experienced teams only took a little more than a week longer to release a product than an inexperienced team.
  • Regardless of experience, most teams chose an iteration length of 2 weeks.
  • More experienced Agile teams gave less estimations and budgets up front (Sounds about right) 🙂

AgileStateOfArt201011
[HT: AmbySoft.com]

Cub Scouts and Agile Scouts – Citizen of an Agile World

After reading The Agile Warriors blog this past week we were inspired.

Inspired to do a terrible photoshop job.

Hey, sometimes inspiration comes in many forms.

Like us being in a StartupQuote.com! <- Check it out!

But one thing you may not know about Agile Scout is that we actually have a similar credo:

The Agile Scout Order of Agility

Live long and prosper!

Did you know you can be an Agile Scout too? Be an Agile Scout!

[HT: AgileWarrior]

Thanksgiving and Agile – 10 Reasons We’re Thankful for Agile

Thanksgiving is a time to reflect on the many things we’ve been blessed with. Today’s turkey special includes our reasons to love Agile.

10 Reasons We’re Thankful for Agile This Thanksgiving:

  1. Customers come first – We love interacting in real-time with our Product Owners. They give us direction and meaning.
  2. Continuous improvement or kaizen – Agile is about always improving over time. It’s a lifestyle!
  3. Huge documentation is #fail – We want to work quicker and faster. Give us (developers) just enough to start kicking butt.
  4. Project course-correction is easy – We welcome changes and can make changes quickly and efficiently. Lessen your change management!
  5. Large projects are history – We can break projects into logical feature-rich chunks. Deliver early, deliver often. Keep it simple!
  6. Developers love quick wins – We can iteratively feel good about what we’re building. Every couple of weeks or so we produce valuable software.
  7. Agile isn’t prescriptive in methods – We can pick and choose different ways to apply Agile in our work environments. We love flexibility.
  8. Agile has created a community of believers and contributors – At a loss for a best way to implement a facet of Agile? Google it. Find Agile thought-leaders. There are plenty out there.
  9. Agile insists on good people who are motivated and flexible – Agile creates a need for best-of-breed-top-quality developers and workers. Design and build your company and teams around people who love challenges!
  10. Agile created the Agile News site: AgileScout.com – Yep. We’re benefactors of this awesome thing called Agile. 🙂

So, what are your top reasons to love Agile?

Continue reading “Thanksgiving and Agile – 10 Reasons We’re Thankful for Agile”