Consulting Consultants IT Consulting
Search 180systems.com       
News Letter Signup
Home
Portals
ERP
CPM
BPI
CRM
About Us
Our People
References
Clients
Services
Software Selection
Business Process Review
Business Case
Project Management
IT Audit
Corporate Diagnostic
HR Management
IT Infrastructure
Strategic Planning
Technology White Papers
Technology Seminars
News & Articles
180 Blog
ERP Systems1
BI2
PSA3
CRM4
SCM5
BPI6
Business Case
Sarbanes-Oxley
IT Strategy
IT Project Management
Office Productivity
Internet
IT Marketing
IT Security
HR
IT Humour
Buyers Guide
Software Selection
Business Case
Total Cost of Ownership
Software Implementation
Accounting Software
Distribution Software
Manufacturing Software
BI2
PSA3
CRM4
Implementation
Software Reviews
ERP Comparison1
ERP Reviews1
ERP Customer Survey1
BI Comparison2
BI Reviews2
PSA Comparison3
CRM Comparison4
Case Studies
Accounting Systems
Manufacturing Software
PSA3
CRM4
White Papers
ERP1
CPM7
Contact Us
Office
Careers
Site Map

Software Selection, Business Process Improvement and Project Management

Wednesday, July 01, 2009

Why Debate? Let Formality and Agility Coexist

June 2009 from Project Times – “From PMI Network to blogs all over the web there is a continuing debate over Agile project management. I find it interesting, if not distressing, that the debate still rages. While there are distinct attributes of Agile methods, overall the basic tenets of formal PM are certainly there. Planning exists, there is a clear point of responsibility and accountability, there is monitoring and control (often a lot tighter and more useful than in more traditionally managed projects) as well as a closing. The predominant differences are in the way these are accomplished and the "weight" of the PM activities. The Agile Manifesto values some things over others, for example "individuals and interactions over processes and tools". This does not mean it seeks to eliminate processes and tools. Valuing the ability of "responding to change over following a plan" does not mean never following a plan…”

180 View – The article is biased to agile project management that includes formal project management as well as being able to not follow it if there are compelling reasons. When I was a bit younger, I was responsible for a multi-million dollar software development project. I was the project manager but I was also responsible for detail design along with a number of other things. I was told by some people that I should be allocating 100% of my time to project management but I never did. It was more like 30%. I was able to reduce the amount if time I spent on project management because of tools that I developed and acquired, and because I was intimately familiar with all aspects of the software. It would be very difficult for anyone on the project team to mislead me. I knew exactly where we stood in terms of quality, scope, timing and budget. So I think project management should adjust to the situation and especially the people involved.

Labels:

0 Comments:

Post a Comment

<< Home

 

 
1enterprise resource planning | 2business intelligence | 3professional services automation
4customer relationship management | 5supply chain management | 6business process re-engineering
  © 2004 One Hundred & Eighty Degrees Systems Limited. All Rights Reserved
Web Site optimized by Toronto Search Engine Optimization | resources