Knowledge (XXG)

Extreme project management

Source 📝

22: 334:
The first step of any management methodology is that extreme project managers have to meet the client or the project stakeholders. Also, a specific analysis must be made to accentuate the value being provided to the client, emphasizing the benefits the client will gain as soon as the project is over.
283:
The extreme approach, conversely, does not run constantly, instead adapting the project activity during the process, which leads in the final stage to a desired result. An extreme project management life cycle model is one that proceeds from phase to phase based on very limited knowledge of goal and
183:
For extreme project management to produce rapid change, it is necessary for all team members to communicate and reach full understanding. This method is used during the project execution and change control process and it is not allowed to be used for overall strategy or project prioritization.
255:
Extreme projects are “a complex, self-correcting venture in search of a desired result” (Doug DeCarlo), where requirements are constantly changing throughout the project as a response to environmental factors such as competition, technology, and economic conditions.
279:
Traditional project management utilizes the "waterfall method", whose purpose is to plan project activity in a straight line. In the traditional approach, each process runs linearly, resulting with what was planned from the beginning.
338:
The extreme project manager is charged with responsibilities to the organization they represent, to the team, and to the project itself. Necessary skills include administrative credibility, political sensitivity and leadership.
296:. Mindset is one of the most important and critical factors related to the extreme project management. In order to change the mindset of a team, there are some main rules for extreme approach for project management: 327:
A project manager is a professional in the field of project management whose responsibility is to plan, execute and manage any project. An extreme project manager has to complete all duties and
122:
The term "Extreme project management" has not been picked up by any of the international organizations developing Project Management Standards. What might be understood as a similar concept is
180:
is evolving very rapidly, extreme projects move forward very fast and allow for teams to work in shorter timelines, being able to better understand and approve each other's ideas and work.
359:
One of the rules that a manager needs to know is that extreme analysis is a way for the clients to know the benefits he will gain, emphasizing its value once the project is completed.
249:
While traditional project management is used for linear work, without any significant changes, extreme project management is ideal for fast-speed projects with unpredictable results.
219:
Traditional project management is defined as an approach which assesses the project through five process groups: initiation, planning, execution, monitoring and completion.
169:
industry is a fast growing domain and in constant development and change. Despite the fact that there are plenty of methodologies and techniques used when it comes to
127: 119:. Advanced approaches to extreme project management utilize the principles of human interaction management to deal with the complexities of human collaboration. 548: 173:, some new, and others that have been used for decades, extreme project management is one of the modern approaches to project management in this industry. 316:
Mindset is defined as “a set of beliefs and assumptions about how the world works” (Douglas DeCarlo). Mindset is the project’s internal programming.
252:
One challenge faced by the traditional approach is that most software development projects' requirements change during the project execution period.
675:, by Jack R. Meredith, Samuel J. Mantel, 8th Edition, Chapter 3: The Project Manager. Publisher: John Wiley & Sons. Release Date: 23 August 2011 379: 284:
solution. Each phase learns from the proceeding ones and redirects the next phase in an attempt to converge on an acceptable goal and solution.
437: 104:
mainly in its open, elastic and nondeterministic approach. The main focus of XPM is on the human side of project management (e.g. managing
657: 615: 43: 703: 672: 319:
A quantum mindset is needed to manage extreme projects in order to provide the project team an opening to change and unpredictability.
208:
2. It instills desire and confidence among stakeholders and it focuses on gaining and sustaining commitment to the project mission.
65: 471: 199:
to the RAP session where a sequence of steps (including planning the project) is run so that the best decisions are taken.
188: 109: 86: 708: 292:
Fundamental to success on an extreme project is the application of both the appropriate complex method and the required
147: 36: 30: 552: 451: 227: 139: 535:, by Doug DeCarlo, Foreword by James P. Lewis, Afterword by Robert K. Wysocki, First Edition, October 2004, Wiley 328: 150:
refers to an "adaptive" type of development lifecycle also called "agile" or "change-driven" with regard to the
47: 533:
eXtreme Project Management: Using Leadership, Principles, and Tools to Deliver Value in the Face of Volatility
192: 152: 385: 105: 342:
The main tasks that an extreme project manager has to fulfill for the project to be successful are:
375: 116: 642: 170: 101: 600: 433: 402:
Xtreme Project Management: Using Leadership and Tools to Deliver Value in the Face of Volatility
496: 123: 370:
Extreme Project Management: Unique Methodologies - Resolute Principles - Astounding Results
532: 196: 427: 688: 573: 697: 630:.By Rob Thomsett. Published by Prentice-Hall, Upper Saddle Creek, New Jersey, 2004 240: 627: 585: 267: 177: 90: 202:
Extreme project management contributes to success in three different ways:
303:
Uncertainty is one of the most common characteristic of an extreme project
331:
at a high-speed level, following the proper extreme project methodology.
166: 211:
3. It is a holistic approach, based on reality, managed by specialists.
293: 94: 222:
The main characteristics of a traditional project management are:
143: 603:, Elaine J. Hom, BusinessNewsDaily Contributor, 25 February 2014 15: 643:
Traditional Project Management vs. Extreme Project Management
618:, By Robert K. Wysocki, Rudd McGary. August 2003, Wiley Pub. 616:
Effective Project Management: Traditional, Adaptive, Extreme
414:
Effective Project Management: Traditional, Adaptive, Extreme
355:
keeping a balance between team members and motivating them
187:
To produce project plans, XPM uses a concept similar to
588:
Critical approach to the concept of XPM. Synopsis. 2001
576:, 2014 Association of Modern Technologies Professionals 660:, by Shaun Ajani. Publisher: iUniverse, 1 January 2002 205:
1. With it, you manage the unknown and unpredictable.
645:. An Apples and Cumquats Comparison, by Doug DeCarlo 176:
Given that requirements are constantly changing and
157:
of a project (an element of the project lifecycle).
100:
Extreme project management differs from traditional
309:Spontaneous changes happen during the processes 191:(RAD) called rapid application planning (RAP). 8: 549:"The Extreme Approach to Managing a Project" 653: 651: 668: 666: 638: 636: 384:. Multi-Media Publications. Archived from 115:Extreme project management corresponds to 673:Project Management: A Managerial Approach 611: 609: 596: 594: 543: 541: 528: 526: 524: 522: 520: 518: 233:Well-understood technology infrastructure 215:Extreme vs traditional project management 66:Learn how and when to remove this message 429:And then came Complex Project Management 259:Extreme projects are characterized by: 29:This article includes a list of general 463: 438:Integrated Project Management Approach 300:Chaotic project activities are normal 7: 689:C2 Entry Page to Extreme Programming 35:it lacks sufficient corresponding 14: 426:Whitty, S.J.; Maylor, H. (2007). 412:Wysocki, Robert K., Rudd McGary. 134:refers to the term "agile" as a 112:techniques and heavy formalism. 93:very complex and very uncertain 20: 586:XPM – from idea to realization. 349:communicating with all parties 1: 189:rapid application development 148:Project Management Institute 108:), rather than on intricate 601:What is Project Management? 725: 704:Project management by type 658:Extreme Project Management 628:Radical Project Management 574:Extreme Project Management 452:Agile software development 408:Radical Project Management 312:XPM increases the security 263:Low possibility of failure 124:"Agile Project Management" 79:Extreme project management 275:Important quality of life 138:(of products; related to 245:Plan-driven TPM projects 239:Experienced and skilled 381:Managing Agile Projects 323:Extreme project manager 50:more precise citations. 352:dealing with obstacles 306:Uncontrollable project 272:Paramount innovation 165:As it is known, the 106:project stakeholders 709:Extreme programming 195:are invited by the 153:product development 117:extreme programming 555:on 18 October 2014 171:project management 102:project management 146:published by the 136:delivery approach 76: 75: 68: 716: 676: 670: 661: 655: 646: 640: 631: 625: 619: 613: 604: 598: 589: 583: 577: 571: 565: 564: 562: 560: 551:. Archived from 545: 536: 530: 513: 512: 510: 508: 493: 487: 486: 484: 482: 472:"ISO 21502:2020" 468: 441: 397: 395: 393: 368:Ajani, Shaun H. 71: 64: 60: 57: 51: 46:this article by 37:inline citations 24: 23: 16: 724: 723: 719: 718: 717: 715: 714: 713: 694: 693: 685: 680: 679: 671: 664: 656: 649: 641: 634: 626: 622: 614: 607: 599: 592: 584: 580: 572: 568: 558: 556: 547: 546: 539: 531: 516: 506: 504: 495: 494: 490: 480: 478: 470: 469: 465: 460: 448: 425: 422: 406:Thomsett, Rob. 391: 389: 388:on 25 June 2012 374: 365: 325: 290: 230:change requests 217: 197:project manager 163: 72: 61: 55: 52: 42:Please help to 41: 25: 21: 12: 11: 5: 722: 720: 712: 711: 706: 696: 695: 692: 691: 684: 683:External links 681: 678: 677: 662: 647: 632: 620: 605: 590: 578: 566: 537: 514: 497:"PMBOK® Guide" 488: 462: 461: 459: 456: 455: 454: 447: 444: 443: 442: 421: 418: 417: 416: 410: 404: 398: 372: 364: 361: 357: 356: 353: 350: 347: 324: 321: 314: 313: 310: 307: 304: 301: 289: 286: 277: 276: 273: 270: 264: 247: 246: 243: 237: 234: 231: 216: 213: 162: 159: 144:PMBoK Standard 132:ISO 21502:2020 85:) refers to a 74: 73: 28: 26: 19: 13: 10: 9: 6: 4: 3: 2: 721: 710: 707: 705: 702: 701: 699: 690: 687: 686: 682: 674: 669: 667: 663: 659: 654: 652: 648: 644: 639: 637: 633: 629: 624: 621: 617: 612: 610: 606: 602: 597: 595: 591: 587: 582: 579: 575: 570: 567: 554: 550: 544: 542: 538: 534: 529: 527: 525: 523: 521: 519: 515: 502: 498: 492: 489: 477: 473: 467: 464: 457: 453: 450: 449: 445: 439: 435: 431: 430: 424: 423: 419: 415: 411: 409: 405: 403: 400:Doug DeCarlo 399: 387: 383: 382: 377: 376:Kevin Aguanno 373: 371: 367: 366: 362: 360: 354: 351: 348: 345: 344: 343: 340: 336: 332: 330: 322: 320: 317: 311: 308: 305: 302: 299: 298: 297: 295: 287: 285: 281: 274: 271: 269: 265: 262: 261: 260: 257: 253: 250: 244: 242: 241:project teams 238: 235: 232: 229: 225: 224: 223: 220: 214: 212: 209: 206: 203: 200: 198: 194: 190: 185: 181: 179: 174: 172: 168: 160: 158: 156: 154: 149: 145: 141: 140:project scope 137: 133: 129: 125: 120: 118: 113: 111: 107: 103: 98: 96: 92: 88: 84: 80: 70: 67: 59: 56:December 2012 49: 45: 39: 38: 32: 27: 18: 17: 623: 581: 569: 557:. Retrieved 553:the original 505:. Retrieved 501:PMBOK® Guide 500: 491: 479:. Retrieved 475: 466: 436:Congress on 428: 413: 407: 401: 390:. Retrieved 386:the original 380: 369: 358: 341: 337: 333: 326: 318: 315: 291: 282: 278: 258: 254: 251: 248: 221: 218: 210: 207: 204: 201: 193:Stakeholders 186: 182: 175: 164: 151: 135: 131: 121: 114: 99: 82: 78: 77: 62: 53: 34: 346:negotiating 142:), and the 48:introducing 698:Categories 559:14 October 458:References 434:IPMA World 420:Literature 392:5 November 178:technology 110:scheduling 31:references 268:deadlines 161:About XPM 155:lifecycle 130:Standard 446:See also 378:(2005). 236:Low risk 167:software 95:projects 91:managing 507:10 July 481:10 July 432:. 21st 294:mindset 288:Mindset 44:improve 503:. 2020 266:Short 126:. The 87:method 33:, but 363:Books 329:tasks 228:scope 561:2014 509:2022 483:2022 394:2012 226:Few 476:ISO 128:ISO 89:of 83:XPM 700:: 665:^ 650:^ 635:^ 608:^ 593:^ 540:^ 517:^ 499:. 474:. 97:. 563:. 511:. 485:. 440:. 396:. 81:( 69:) 63:( 58:) 54:( 40:.

Index

references
inline citations
improve
introducing
Learn how and when to remove this message
method
managing
projects
project management
project stakeholders
scheduling
extreme programming
"Agile Project Management"
ISO
project scope
PMBoK Standard
Project Management Institute
product development
software
project management
technology
rapid application development
Stakeholders
project manager
scope
project teams
deadlines
mindset
tasks
Kevin Aguanno

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.