Send a suggestion!

We're building a brand new version of the site, and we'd love to hear your ideas

Members

Technology Zones

IBM Learning Center

Articles

Hosted By

MaximumASP

Info

[3231] Pro Developer - Throwing Money Out the Window

Last post 01-13-2003 10:57 AM by davepamn. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 01-01-1999 12:00 AM

    [3231] Pro Developer - Throwing Money Out the Window

    This thread is for discussions of Pro Developer - Throwing Money Out the Window.

    • Post Points: 0
  • Advertisement

    • Red Gate Software

    Advertisement

    Want to boost your .NET application performance?

    Some developers always seem to write efficient and lightening-fast code. What is their secret? It’s ANTS Profiler. “We improved the performance of the application up to 10 times” Dan Ports, Intrigma.

    Try it for yourself now.

  • 01-13-2003 10:57 AM In reply to

    • davepamn
    • Top 500 Contributor
    • Joined on 02-16-2002
    • Addicted Member
    • Points 195

    Design Specification Extreme Pro

    Design Specification Extreme Pro

    Project management is a sophisticated science.  A new emerging discipline in software engineer called Project Management Principle (PMP body of Knowledge) takes systematical approach to solving some of the common problems associated with software failure.

    In reading the article I reflected on some of the PMP principles such as scope, stakeholder buyoff, activity planning, and risk management.  The flow of PMP is to complex to demostrate in this response but definately most software fails because of lack of planning and design.  

    I used the PMP model while working as an outsourcing SPA.  I found it took 95 percent design and planning and 5 percent code to complete the project.   Software development is that political.   The technical risks rarely inhibited the release of a program.  Object orient technologies and database technologies are extremely flexible.  

    The real challenge is to bring the business model into focus: business requirements, assumptions, constraints, required resource, and scope (budget, time, resource).   The PMP way advocates increased CMM levels to achieve its objectives.

    Let say extreme programming principles can fit inside a PMP framework.  The PMP framework is designed to produce documentation that brings the business teams into focus and scope.   Deliver a product with exactly the desired features wanted, no more no less.

    In short,  I sympathize with the authors fustrations, but a more beautiful design exists to reduce lose and fustration.   Management incompetence is an enemy, but systematic approaches can reduce risk of failure.  Let the failure occur on paper first.    Using PMP, I had a few project halted because it didn't fit the business needs.  The cost was minimal because it was a documentation cost.   I recommend, One analysis handling manage numerous development projects, flexibility and cooperation among the team members, and customer center methodologies.  Resource matrixes provide availability schedules and extreme programming principles ensure reliability and reuse.   Consider this as an approach to reduce fustration.

    • Post Points: 0
Page 1 of 1 (2 items)