tag:blogger.com,1999:blog-8321975.post2125068322018097509..comments2023-08-18T11:34:36.582+01:00Comments on Silicon Glen: PRINCE2 + AGILE = Common sense?Craig Cockburnhttp://www.blogger.com/profile/13627819863234028263noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-8321975.post-45153580649006353692016-01-20T14:13:01.002+00:002016-01-20T14:13:01.002+00:00Nice one i found it useful,
G.S.R.Murthy,
Charte...Nice one i found it useful,<br /><br />G.S.R.Murthy,<br /><a href="http://vijayaengineering.com/chartered-engineering" rel="nofollow"> Chartered Engineer</a>,<br />India.G.M.PRASHANTHhttps://www.blogger.com/profile/11863032501007491035noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-1424810524485269342011-06-24T18:39:23.143+01:002011-06-24T18:39:23.143+01:00Hi just written this article you all need to read....Hi just written this article you all need to read. I believe PRINCE2 is AGILE so the + is not nessary. Old wine in new bottles in my view.<br /><br />http://eprince2.com/articles/prince2-is-agile/2011/03/17/Kevin Bradyhttps://www.blogger.com/profile/06108582644292507723noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-28544183661188077582010-12-05T13:54:39.487+00:002010-12-05T13:54:39.487+00:00Following this blog post from 2008, I am pleased t...Following this blog post from 2008, I am pleased to announce that in addition to all the hands-on experience and writing here about it, I am now certified in DSDM Atern having passed my exam recently with flying colours.Craig Cockburnhttps://www.blogger.com/profile/13627819863234028263noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-79346708330139764682010-06-20T08:44:41.039+01:002010-06-20T08:44:41.039+01:00A decade ago I got interested in software procurem...A decade ago I got interested in software procurement (See http://www.faxfn.org/07_software.htm) so I'm pleased to see this authoritative discussion. What I was unable to discover was any literature that assessed the success rate of PRINCE2 - or its predecessors.<br /><br />Is there any?Unknownhttps://www.blogger.com/profile/14219623853167716273noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-84411876290721487642009-11-19T20:31:32.459+00:002009-11-19T20:31:32.459+00:00I like this article....well done :-)
I think to a...I like this article....well done :-)<br /><br />I think to answer one of the later questions, PRINCE2 exists in companies because: <br />1. they do not want to re-write a methodology, <br />2. they want a COTS style solution with defined training programs, and, <br />3. there is little else out there that can be customised to fit any project. <br /><br />As for Prince2 vs Agile....<br />From a project stand point Prince2 would control the framework of a 'Programme' i.e. capture what the business requirements (even if they are high level), benefits of these requirements, draft an overall project plan. One of the components within this plan would be a work package to 'create a system or tool'...then that work package can use what ever method it likes providing it provides the required outputs required by Prince2 i.e. Quality Register et al. <br /><br />I find it hilarious when people say that Agile and Prince2 are different PM methods and not compatible. One is a Project methodology and the other is System Development Life Cycle (SDLC). SDLC's 'always' sit within a project plan. After all, how would they otherwise get backing and business justification? From my experience Agile is not great at enforcing the customer to detail benefits where as Prince2 mandates the business case which goes through the board (or who ever is providing the budget) for approval through to implementation and is used to quantify a success!Unknownhttps://www.blogger.com/profile/13096111293895441266noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-46961512010299144762009-02-13T12:19:00.000+00:002009-02-13T12:19:00.000+00:00Good article, but what it neglects to probe is why...Good article, but what it neglects to probe is why with the evidence of PRINCE2 failures do so many organisations (including the public sector) continue to use it slavishly for IT projects. <BR/><BR/>In my experience it comes back to procurement - with many/most customers pushing for fixed price projects with payment increasingly being tied to delivery of pre-agreed milestones (e.g. documented & signed-off). Agile doesn't get a look-in because procurement people don't buy the argument that any up- front cost with up-front scope is just delusional given the fact of change/clarification. The procurement person who signs a contract saying that "Agile promised to get me closer to my real requirements more quickly with less waste" would be fired the moment something went awry.Unknownhttps://www.blogger.com/profile/05307565766873306662noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-62740776910769716332008-06-04T22:10:00.000+01:002008-06-04T22:10:00.000+01:00There's now a LinkedIn group for PRINCE2 professio...There's now a LinkedIn group for PRINCE2 professionals<BR/><BR/>See here: <A HREF="http://www.siliconglen.com/news/2008/05/prince2-on-linkedin.html" REL="nofollow">Prince2 LinkedIn</A>Craig Cockburnhttps://www.blogger.com/profile/13627819863234028263noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-52965897829775202612008-04-25T15:10:00.000+01:002008-04-25T15:10:00.000+01:00From experience, I feel that one of the clear bene...From experience, I feel that one of the clear benefits of Agile type approaches to software development is that clients often don't know what they want or need until they actually see working software, something the early deliverable nature of Agile achieves.<BR/>This is particularly poignant in public sector procurement which tends to feature <A HREF="http://www.agile-lab.co.uk/labels/multi-agency.html" REL="nofollow">multi-agency, 'clients'</A> that want completely different things. These types of projects tend to become hampered by Prince2's inability to deal with a competing client agenda, something that Agile can do very effectively.<BR/>Prince2 also treats change as something to be minimised and managed rather than be recognised as an integral part of the creative and developmental process as is the case within Agile.<BR/>I agree that Agile and Prince2 can live together happily, the problem for me is that for many projects for which Prince2 is used, it is not the best option.Matt Gouldhttps://www.blogger.com/profile/12973596166136769799noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-47334533849065912872008-04-03T12:02:00.000+01:002008-04-03T12:02:00.000+01:00Great blog. I would be please if you could look at...Great blog. I would be please if you could look at www.princelite.co.uk. I intend to check out all of your references. You talk a lot of sense. <BR/><BR/>PeterPeter Mhttps://www.blogger.com/profile/09355311330844709727noreply@blogger.comtag:blogger.com,1999:blog-8321975.post-52778550985007825552008-02-02T18:49:00.000+00:002008-02-02T18:49:00.000+00:00I agree with you that on some cases Prince2 and ag...I agree with you that on some cases Prince2 and agale can be a good combination. In most cases I think it is not.<BR/>I do not agree that "Control is clearly a Good Thing". <BR/>And especially combined with agile.<BR/>Agile is about giving the responsibility to the team.<BR/>I do understand that in some companies Prince2 is the default methodology. I also understand that it (prince2)might not be a good thing for all projects. So by combining both methodologies (Agile is not a methodology but that is another discussion) they hope to get the project going, and still getting the project finished on time etc.<BR/>For me his is a sign that they avoid discussion. If Prince2 does not work for that kind of project, it should be made clear to upper managment that having a default project methodology is not a good thing for this company. <BR/>Avoiding that kind of hard discussions at the beginning of a project is a bad start. It might came back later to hunt you. <BR/>In most of these cases Scrum + XP is a better combination.Anonymousnoreply@blogger.com