Posted by Gregg Kellogg
Thu, 02 Nov 2006 18:00:00 GMT
Many software projects fail to deliver on-time and on-budget and a factor in that is normally inefficient project communication. Studies have shown that software teams that consistently deliver on-time and on-budget communicate in an effective manner. These teams stay in contact constantly, but wisely use each other’s time during the communication process and are careful not to waste other people’s time.
Below are some tips for enhancing project communication when working in software development projects:
Read more...
Posted in Design | Tags Scrum | no comments | no trackbacks
Posted by Gregg Kellogg
Thu, 02 Nov 2006 18:00:00 GMT
Working with legacy software systems provides its own considerations, but there are some general goals that can be stated for web-based software applications. To the degree that the nature of system upgrades substantially touches these areas of system design, it is important to consider the following goals within the system design.
Well designed applications should meet the following goals in order to provide lasting value:
Read more...
Posted in Design | no comments | no trackbacks
Posted by Gregg Kellogg
Thu, 02 Nov 2006 18:00:00 GMT
A popular trend in systems development circles is the so-called Extreme Programming Paradigm. XP has proven to be quite effective at rapidly producing system functionality, and it includes many practices that should be considered by any development team (e.g., Test Driven Development or TDD). However, there are many pitfalls to XP that don’t necessarily make it the best technique for many organizations.
Read more...
Posted in Design | no comments | no trackbacks
Posted by Gregg Kellogg
Tue, 31 Oct 2006 20:10:00 GMT
Of paramount concern in managing large development efforts is the need to ensure that the application remains relevant and maintainable and can be kept up-to-date with the requirements of the rest of the organization.
The danger of a long running project managed by a limited pool of developers is that the original requirements and goals of the system can be lost in the face of multiple enhancements. This can lead to a system that is arcane, does not reflect the actual needs of the department, and (most importantly) is over-reliant on the internal knowledge of the development team. This poses a substantial risk to the business that relies on the system for day-to-day operation.
Fortunately there is a long standing body of Industry Best Practices that have been used to successfully manage the lifecycle of large-scoped projects.
Read more...
Posted in Design | no comments | no trackbacks
