Short post, it's late :-)
Interesting article at BPM enterprise about BPM for software development
(link: http://www.bpmenterprise.com/content/c071022a.asp)
What's missing is a key metric: the likelyhood/trackrecord that we deliver on scheduled date.
It's funny - all the effort in various software development methodologies.
In a way it's all (new TLA:) ITPM. IT Process management....
As a BA/BPM specialist, and 15 years of IT development/projectmanagement experience, it often happens that when starting on a new or running project, 20 - 40% of my time is actually spent on process improvement... in the project. E.g. implementing, structuring, refining and improving requirement management process, issue management, testing approach etc. :-).
Is your job also often ITPM?
No comments:
Post a Comment