Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Monday, 28 May 2007

Agile people working in a non-agile world

Posted on 07:01 by Unknown
Implementing an agile development frame work, such as Scrum, does not solve your company’s problems but helps identifies them. My current company has implemented the scrum agile management frame work. The initial results from the product mangers point of view have been quite interesting:
  • Various stakeholders gradually changing their behaviour as they record their required enhancements and bugs fixes in the product backlog rather than emailing the Product Manager and CC-ing half the company hoping that the long lists of people who have been copied on the email will somehow generate momentum to make it happen instantaneously.
  • An understanding from commercial stakeholders that there will be periodic releases and therefore new features and enhancements will be released within a set time frame.
  • Total transparency as groups of business and product owners meet each morning with the Product Manager and engineering teams to review commitments made the day before, discuss today’s commitments and identify impediments that stand in the way of the team delivering on commitments.

The implementation of an agile frame work had certainly helped in delivering software incrementally to the end users but has at the same time exposed a number of cross company issues and bottlenecks that could threaten return on investment (ROI).

Product Managers are agile managers: traditionally interfacing between the engineering team, various other technical teams and commercial/business stakeholders. Being in a pivotal position places them in the ideal place to act as exponents to change – assisting in changing a non-agile company into an agile one. This is especially true of Product Managers who have embraced an agile frame work, tasted the fruits of its success (in the software development life cycle) and now want to move the boundaries of agile working from beyond the engineering team(s) to other areas of the company. However such a programme whether formal or informal would require the full backing of chief executives who after all claim, according to a recent McKinsey survey on building nimble organizations, ranked agility as “very” or “extremely” important to their business success – with 91% stating that it had become more important for their companies over the past five years.

For more on this topic read the 1st half of : Think Big Think Agile Product Management

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in Agile, Product Management, ROI | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Part #9 The role of the Product Manager in Scrum
    Scrum has three key roles: #1 The team – who owns the sprint backlog and are responsible for estimating. functionality and fulfilling th...
  • Agile Product Management Framework
    There are many good product management frameworks available - however, I thought I would create an agile product management framework that i...
  • Interview Questions for Product Managers
    Several months ago I spent a lot of time interviewing potential Product Manager and Lead Product Managers to head up a product team. List...
  • Part #5 How to adopt Agile Product Marketing
    The Agile Product Manager works closely with the engineering and technical teams working with in an agile framework such as scrum. The ado...
  • Part #10 Justifying Time to Research with Agile
    Agile Research I worked for a company that designed and manufactured niche signal processing equipment for the broadcast industry. Part of t...
  • From Software Engineer to Product Manager to Founder of SVPG - Interview with Marty Cagan
    Marty Cagan has worked for several leading Hi Tech companies such as Hewlett-Packard, Netscape Communications, America Online, and eBay. Du...
  • How Product Managers can estimate business value using agile techniques
    We recently finished a scrum sprint; during the sprint review the technical team gave a demonstration, to senior business owners, of the ne...
  • How Product Managers can push back at an interview
    Interviews are about persuading the interviewer(s) that you are the right person for the job. That you will be able to deliver the goods ...
  • Part #6 How Everyone Can Get Involved in Agile
    I mentioned in an earlier post that I was adopting scrum (an agile development frame work). At first implementing scrum identified quite a f...
  • Part #1: Implementing an Agile Sales Framework
    By their very nature sales people are agile in their approach to selling products and services. A good sales rep will intuitively carry out...

Categories

  • Agile
  • Agile Manager
  • Business case
  • Developers
  • Engineers
  • Increase revenue
  • Innovation
  • interview
  • Knowledge Management
  • PM interviews
  • Product Development
  • Product Management
  • Product Manager
  • roadmap
  • ROI
  • Scrum
  • ScrumMaster
  • stakeholders
  • strategy
  • Technology
  • Test Analyst
  • Tips
  • Tips + Tools
  • Value chain analysis
  • waterfall
  • Your Career

Blog Archive

  • ►  2013 (3)
    • ►  June (1)
    • ►  May (2)
  • ►  2010 (4)
    • ►  October (1)
    • ►  July (3)
  • ►  2009 (5)
    • ►  August (1)
    • ►  July (1)
    • ►  June (1)
    • ►  March (1)
    • ►  February (1)
  • ►  2008 (43)
    • ►  December (2)
    • ►  September (1)
    • ►  June (2)
    • ►  May (2)
    • ►  April (2)
    • ►  March (9)
    • ►  February (11)
    • ►  January (14)
  • ▼  2007 (34)
    • ►  December (1)
    • ►  November (5)
    • ►  October (2)
    • ►  September (2)
    • ►  August (4)
    • ►  July (4)
    • ►  June (3)
    • ▼  May (3)
      • Pain without gain (ROI) or pleasure with gain (ROI).
      • Agile people working in a non-agile world
      • Being up front during an interview
    • ►  April (4)
    • ►  March (6)
Powered by Blogger.

About Me

Unknown
View my complete profile