 |
|
|
If you own a website that related to software development you are welcome to participate in our website. |
|
Join our partner list |
Programmers online portal |
Web Development Forum |
|
 |
 | |  |
 |
 |
Article - Software Development And Java Programmers on Web Development Forum |
 |
Website about Application Development - Programmers portal. Other useful information: http://www.ambysoft.com/services/
triangle " of software development:
development (AMDD) approach to software development. It is one of the
J2EE: EJB, JSP, Servlets, JSF, JSTL, JCA, JMS, JTA, JNDI, JDBC, JMX, RMI, etc.
Frameworks: Struts, Hibernate, JPA, iBATIS, JBoss AOP, Spring, JSF, AJAX, GWT, YUI, Flex/Flash, JUnit, and Jakarta common libraries.
Integration: Web Services on Axis and WebMethods; as well as the Web Service Standards such as SOAP, WSDL and UDDI.
| For you information - A Programmer Is Someone Who Writes Computer Software. The Term Computer Programmer Can Refer To A Specialist In One Area Of Computer Programming Or To A Generalist Who Writes Code For Many Kinds Of Software. One Who Practices Or Professes A Formal Approac |
The "Broken Iron Triangle" Software Development Anti-pattern - triangle " of software development:
Software development projects often fail because the organization sets unrealistic goals for the " iron
The development team has
The "Broken Iron Triangle" Software Development Anti-pattern
The "Broken Iron Triangle"
Software Development Anti-pattern
Home |
Articles |
Agility@Scale Blog |
Books |
Podcasts |
Contact Me |
Mailing List |
Site Map
Scope (what must be built)
Schedule (when it must be built by)
Resources (how much it must cost)
failed at renegotiating the situation, and is forced to try to deliver
under those constraints anyway. In the end, if the project team
delivers at all, the quality of the delivered product suffers and the
project is almost always late and over budget anyway. To be
effective, project managers must understand the implications of the iron
triangle.
Figure 1 . The Iron Triangle.
Note that refusing to recognize the
implications of the iron triangle isn't the only cause of
project failure, it just seems that it's one of management's more popular
approaches to hamstringing an IT project. In many ways, we really need to
question the ethics of "fixed-price" IT projects.
Motivation
The fundamental problem is that each major group of stakeholders has a
different, and often conflicting, set of priorities. IT professionals lean
towards building high-quality systems, financial people seem more interested in
the overall cost, senior management in the schedule, and end users in the
scope. Although these are clearly stereotypes we’ve all been in situations
|
|
|
|