Tech Support

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

Thursday, 7 June 2007

Identifying Agile Organisations, Functions and Roles

Posted on 12:16 by Unknown
There currently seems to be a strong move towards agile software development. Engineering teams and I.T. departments are adopting one agile method or another. However the conversion of software teams, to agile, does not naturally result in the other areas of a company adopting an agile method of working. The question is why should other areas adopt an agile approach to work? The answers is simple - because it is important to 91% of CEOs who are looking at how their company’s will develop over the next 5 years.

Some departments and functions could improve their performance by working in an agile way, while it may not be at all suitable for others. Some departments and functions (in some companies) do work in an agile way but we probably don’t recognise it. While it would be totally inappropriate for others to even consider adopting an agile way of working.

This article is an introduction to a 10 part series on how Product Managers and Engineering teams could influence various aspects of a company to help them identify and/or adopt an agile approach to working. It is also important for technical people to be aware of how other departments operate - many jobs, positions & functions: CEO, Managing Director, COO, Sales, Marketing, Product Management etc... in Hi-Tech companies are performed by people who have strong technical/engineering backgrounds.

The areas that will be covered are as follows:
  1. Agile sales
  2. The agile chairperson or meeting co-ordinator
  3. Agile training
  4. Agile customer support
  5. Agile product marketing
  6. Agile for everyone
  7. Agile software testing
  8. Agile management
  9. Agile product manager
  10. Agile research

Being an agile company means that you’re a competitive company – being competitive increases your chances of an increased return on investment (ROI ). An increase in ROI means more investment in technology, training and research and ultimately to greater job satisfaction. Hope you enjoy and contribute to the series.

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in Agile, Product Management | 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)
      • Part #2: Agile meetings run by an agile chairperson
      • Part #1: Implementing an Agile Sales Framework
      • Identifying Agile Organisations, Functions and Roles
    • ►  May (3)
    • ►  April (4)
    • ►  March (6)
Powered by Blogger.

About Me

Unknown
View my complete profile