Here's a fascinating (to me) blog entry contrasting Apple engineers and Microsoft's.
Data Structures As Culture [scifihifi]
I've long been interested in these sorts or correlations or indicators, as I see them too and heavily use them in my interviewing.
Beyond the correlations/indicators though is the just as interesting aspect of this which is to do with simplicity. Developers, architects, solution designers, and so on - are (mostly) terrific at creating far more technology complexity than is justified.
Are ther plans to develop and deploy the FDD approach to Visual Studio Team System 2005?
Thanks
Al
Hi,
sorry but I still need some clarification concerning the currently planned and coming up workshops . Under Certification it's said:
Currently, you achieve FDD Aware status through either of the two Accredited FDD training workshops. What this says is that you are Certified as FDD Aware as you have successfully completed Accredited FDD training. If you successfully complete both Accredited workshops you achieve Certified FDD Associate status which is the foundation/essentials level.
Hi,
I currently working as an Architect in a large scale, quite complex, systems integration project involving integrating COTS (ERP, SCM) with in-house developed components (Data Warehouse, Enterprise Service Bus (Middleware), Integration Adaptors/Wrappers) and interfaces to legacy and customer / supplier systems.
We have major issues with requirements. The solution is supporting a brand new area of business the company has never been in before. Therefore, end users and managers in the business cannot provide us with any level of detailed requirements, only the high level business need. To compensate a good proportion of the team members have extensive experience in the domain. We already have an initial release of the solution live and successful. The current release we're working on is sustantially expanding the "solution footprint". We also have the issue of iterating requirements against COTS capabilities which, in turn, causes flux in design requirements for the middleware. For example the ERP consultant implements a particular use of an ERP object (e.g. process, states etc), the development team begin to map those states into events on the middleware for integration with other components, then a subsequent iteration with the business changes elements of the ERP model causing a number of design assumptions in the middleware to become invalid. We are protecting ourselves against this to a certain extent through the design of the middleware - extensive use of XML and XSLT in an open standards J2EE / JMS framework.
ITPS is pleased to announce the release of FDDTracker v1.2 which includes the following new functionality and enhancements:
- Full support for Project Aspects
- Document Management
- Support for Estimates / Actuals
- Support for Releases / Iterations
- Integrated LDAP (Active Directory / Domain) support
- Trend Report
- Progress by Aspect Report
- Feature Notes Report
- Ability to define milestone headings
- Ability to define status colours
- Data Export from Feature List
- Keyword Search in Feature List
- Enhanced Feature Maintenance
- Enhanced Options Maintenance
We are pleased to announce that the June 2005 release of FDD Manager, which includes the following enhancements, is now available for download.
FDDTools Release 0.8.5 is now available on Sourceforge.
This release includes UI enhancements improving usability, simple print functionality (print the currently displayed project tracking graphic), and improvements to the "Save As Image..." feature to save the image without additional white space around the image.
We encourage everyone to download the new version and provide comments and feedback.
What are some of the key difference between FDD and MSF Agile?