• Products
    • Demos
    • TaskMap Standard
    • TaskMap Pro
    • Capture for Excel
    • TaskMap Central
    • Upgrade
  • Downloads
    • Trials
    • Templates
    • Free Role List
  • Training
    • Self-paced Tutorials
    • Online Seminars
    • Calendar
  • Solutions
    • ITIL Suite
    • SOX Expert Suite
    • SPM Roadmap
    • Consulting
    • Process Conversion
    • Process Templates
  • BPM Blog
    • Process Mapping
    • Process Discovery
    • Process Analysis
    • Improvement
    • Change Management
    • Articles
  • Support
    • Product Support
    • TaskMap
    • FAQ's
    • Contact
    • Self-Paced Tutorials
  • About
    • Contact
    • Partners & Resellers
    • Background

  • About the BPM Blog
  • BPM Blog Sitemap

BPM Blog

BPM made simpler

« Additional displays: Are they worth the money?
Customized process mapping »

Agile methodology: The case for a blended Agile

Oct 26th, 2011 by TaskMap

 

Most of my life I have been involved with projects. Many of them large, complex and involving creating innovative software products; my career has not been for the fainthearted.

Over the course of these last 25 years a great deal of water has passed over the dam in the development of Project Management methodologies. Also process based technologies have made for a more systematized approach to creating successful products.

During this time many of these methods have become institutionalized, certified, authorized and pasteurized. We now have PMBOK, Prince2, Agile, Scrum, CMMI, ISO, ITIL and a whole lot more to choose from to prove our credentials in an industry discipline that had little to start. Times have changed.

Agile may be been a late comer to the Project Management ball, celebrating a ten year birthday, but it has made a huge impact. Because of the radical nature and departure from “other project management” methods then in vogue, it got noticed. It also focused heavily on software development, which seemed to be (and perhaps still is), more art than science.

The squabbling continues

Articles abound purporting the benefits and problems associated with one method or another. Agile has been no stranger to this criticism; however the search for innovation does not just lie in technology development, but also in the manufacturing process, itself. The difference being not just one way doing the work, there are many.

The tremendous improvements that are core to Agile development include; transparent and continuous communication within development teams and customers; willingness to listen and integrate changing requirements and total interdependence of team members. These are foundational principals that should be a part of any project; regardless whether the end product is a software system or a residential home.

However, believing that Agile alone will instantly create a Kumbaya atmosphere for your project is not a good assumption. Team members also need structure to work successfully, and much the elements from other Project Management methods can be integrated with Agile to get the best of both worlds.

Imagine having an argument for which drink is best … coffee or milk? They are different but both serve a purpose to satisfy a need for refreshment, and provide nourishment. The bottom line is many like to have both coffee and milk together. So goes it with Agile and Non-Agile Project Management methods; different but not incompatible.

Researcher and Project Managers agree on a blended approach

Many organizations are now taking a blended approach and organizations such as Forrester Research recommend including traditional and Agile skills, traits and methods.

Project Management’s PMBOK advantages

Agile promotes

· Clear guidance on project initiation and closure.

· Communications management and project integration management.

· Project cost management.

· Risk management

· Cross-functional, empowered teams.

· Flexibility and adjustment throughout a project.

· Encouragement of strong working relationships with customers.

· Just enough rigor and documentation


The table above illustrates the benefits of such a blended approach as recommended by Forrester Research

There are thousands of projects that individual Project Managers (Owners) where the benefits of such a blended approach have been espoused. So the combination of different methodologies is now becoming very commonplace in many industries, not just software development. When you see leading legal firms such as Seyfarth adopting lean and Six Sigma, you just know that things are changing.

Agile Stepping Stones Approach

As a part time ski instructor in the winter, I have come to learn that you need a lot of skills, lessons and techniques in your bag. The Professional Ski Association of America teaches these skills to instructors with a combination of observation, lesson planning and execution is required. If a student cannot learn a technique through one approach, then you can try three others that may resonate with them.

This approach is known as stepping stones. Where progress is made by selecting different skills, models and examples and then traversing up the learning curve from there.

We can learn much from this approach by applying those agile attributes and methods and creating “our own agile blend”. This will allow an organization to take the best of each approach as it relates to their particular problem or project.

As an example, much of my current software development work is carried out across different countries and time zones. By using a more “heavyweight” documentation approach, there is a reduction in corrective iterations of the software that could be very costly. So we put more emphasis on user interface designs and detailed use cases to remove ambiguity from the early stages of a project. Conversely we use all available communications tools in reviewing and problem solving during the development cycle. These include Web conferencing, Chat, Skype and revision controls.

By picking our spots to use Agile, it may well be that less is more. We only force the benefits of agile where they are adding value to the project, and avoid methodology wars amongst our colleagues and teams. Just was different materials are used in creating products, we can apply the same principles in techniques and perhaps make it to the other side with our team and goals intact.

 

Tags: agile development, agile scrum, cmmi, continuous communication, fainthearted, foundational principals, innovative software, interdependence, itil, manufacturing process, project management methodologies, project management methods, radical nature, software products, software system, team members, technology development, vogue, whole lot, willingness

Posted in Project Management

One Response to “Agile methodology: The case for a blended Agile”

  1. BPM Blog summary for week ending 28 October 2011 « BPM Blog says:
    October 28, 2011 at 3:12 pm

    [...] Agile methodology: The case for a blended Agile [...]

    Reply

Leave a Reply

Click here to cancel reply.

  • Archives

    • March 2012 (1)
    • February 2012 (3)
    • January 2012 (4)
    • December 2011 (11)
    • November 2011 (16)
    • October 2011 (17)
    • September 2011 (20)
    • August 2011 (21)
    • July 2011 (21)
    • June 2011 (22)
    • May 2011 (22)
    • April 2011 (23)
    • March 2011 (26)
    • February 2011 (28)
    • January 2011 (31)
    • December 2010 (31)
    • November 2010 (20)
  • Recent Posts

    • Business Process Modeling
    • Education
    • The issue of organizational culture
    • A VERY SHORT HISTORY OF PROCESSES
    • Process Dashboards: Identifying and flagging risk levels
    • Process Dashboards: Analyzing timeframes
    • THE CASE FOR PROCESS DASHBOARDS
    • Is 2012 the year that version control finally takes hold?
    • How to listen carefully to your team–Reflective listening skills overview (Part 8)
    • How to listen carefully to your team–Reflective listening skills overview (Part 7)
    • How to listen carefully to your team–Reflective listening skills overview (Part 6)
    • How to listen carefully to your team–Reflective listening skills overview (Part 5)
    • How to listen carefully to your team–Reflective listening skills overview (Part 4)
    • How to listen carefully to your team–Reflective listening skills overview (Part 3)
    • How to listen carefully to your team–Reflective listening skills overview (Part 2)
    • How to listen carefully to your team–Reflective listening (Part 1)
    • TaskMap Update: version 4.0.5
    • BPM BLOG Summary for week ending 2 December 2011
    • The Tutorials are coming … the tutorials are coming
    • The psychology of spending and how it can help BPM ;-)
    • Happy Thanksgiving
    • BPM Blog–The need to refine
    • Processes as instruction tools
    • BPM Blog Weekly summary 11.18.2011 with video blog
    • Project and Processes (responses to the questions)
    • Projects and processes
    • Thinking things through
    • Happy 11.11.11 and BPM Blog summary
    • TaskMap Automated tutorial: TaskMap Capture for Excel
    • Customizing fields in TaskMap 4 Professional
    • Prioritization in your life
    • The need to refine
    • Happy Anniversary BPM Blog: A good first milestone
    • Training the trainers
    • Power
    • BPM Blog summary for week ending 28 October 2011
    • Customized process mapping
    • Agile methodology: The case for a blended Agile
    • Additional displays: Are they worth the money?
    • BPM Blog summary week ending 21 October 2011
    • Thoughts matter: How thoughts affect our actions in everyday life
    • BPM Summary of automated tutorials on the TaskMap menu
    • Automated tutorial—Save as process folder
    • Automated tutorial—Task Links and how to use them
    • Automated tutorial for Task Details
    • TaskMap Tutorial—Save as PowerPoint
    • Check my TaskMap
    • BPM Blog summary week ending 7 October 2011
    • Renumbering Tasks in TaskMap
    • Customizing roles names in TaskMap
    • Adding tasks to a Page–add task to page Dialog
    • How to add tasks to pages using the auto connect feature in TaskMap
    • BPM Blog Summary Week ending 30 September 2011
    • Towards Perfection
    • BPM in the Legal Profession
    • BPM BLOG SITE MAP
    • Rigor and our business processes
    • BPM Summary Week ending 23 September 2011. The Case for a Blended Agile
    • The Case for a Blended Agile: Part 4-Agile Stepping Stones Approach
    • The Case for a Blended Agile: Part 3-What a blended approach looks like
  • RSS Get the BPM RSS feed

  • Posts by category

    • Change Management
    • Compliance
    • Law Processes
    • Legal processes
    • Org Charts in Visio
    • Process Analysis
    • Process Discovery
    • Process Improvement
    • Process Mapping
    • Project Management
    • Uncategorized
  • Tags

    best practices bpm budget business analyst business process category change change management computing group dashboard decisions discovery discovery phase efficiency flowchart flowcharts goals and objectives governance harvard job management change management project map methodology mike cunningham milestones personality process documentation process improvement process mapping process maps project management project managers quality standards return on investment risk role names sox compliance target task library team members technorati time and money timeframe Visio willingness

Home • Products • Downloads • Templates • BPM Blog • Training • Contact Us • SiteMap

Copyright © Harvard Computing Group, Inc., 1994-2011. All Rights Reserved. TaskMap is a registered TradeMark of Harvard Computing Group.
Harvard Computing Group, 225 Cedar Hill Street, Suite 200, Marlborough, MA, 01752, USA Tel: 978-800-4590