Controlled-Chaos Software Development
- Topics:
- Product Development and Design
- Tags:
- Business Process Reengineering (BPR),
- Team,
- Systems Development,
- Software/Web Development,
- Software Development,
- Ooa/Ood/Oop,
- Object-oriented,
- Management,
- It Operations,
- ISV,
- ...
- Source:
- Control Chaos
FREE Registration is required
Overview: We have formalized empirical, chaos-tolerant development processes into a macro process named Scrum. The detailed micro processes of OO, BPR, and other techniques are implemented within this macro process as needed and as standardized within an organization. Systems development is not now, and may never be, a cookbook process. Component-based development already eases our job, but the intelligent, adaptive, ongoing interaction of a project team and the environment is mandatory to successful product delivery. Controls ensure that that product is the best possible that could be produced by that team, given that technology, for that environment. This paper presents a macro-process for developing object-oriented or clean-interface systems. The macro-process, Scrum, is a formalization of development processes used by many Independent Software Vendor's (ISV's).
(Is this item miscategorized? Does it need more tags? Let us know.)
Format: PDF | Size: 161KB | Date: Aug 2004 | Pages: 12




