We've had several private emails on when the next FDDI update will be. FYI - we're going to be taking this effort in a different direction. One issue is scope and outcome: interchange or report generation? Another issue is implementing and using XSD.
Jeff
We are pleased to announce that the April 2006 release of FDD Manager, which includes the following enhancements, is now available for download.
Feature-driven development requires clear communication between the project team and the customer. A primary product of this communication is the project schedule for feature deliverables. Not all project management tools are well understood by customers. At the highest level, a customer is primarily focuses on cost, schedule, and risk (CSR). Not everyone can clearly identify CSR when reviewing a Gantt chart such as those used in Microsoft Project (tm). I propose a simpler technique for illustrating and managing schedules for Agile projects. I propose that using line graphs is a simpler and easier way to convey CSR. I've put together an example at FeatureDriven.com. Schedules for plans and progress lines clearly show where develop is ahead or behind, allowing simple visualization of schedule concerns, potential for cost savings or overruns, and completion risks. In addition, I suggest the use of indicator annotations (red, amber, and green) to provide a visual guide to subjective assessment of risk (green - a head, amber - on track, and red - concern).
Seth writes about marketing and this is a very interesting and balanced post about process.
I am looking for a brief listing of steps to be followed if I were to develop a new product using SCRUM Vs FDD. (example, Step 1: Document all your features should be documented in XYZ document Step 2: There should be a consensus meeting every morning etc). Also, are there any publicly available templates for each of these methods on top of which I could develop my own (or use as-is)?
I want to rapidly develop a product devising a method out of FDD and SCRUM and am looking for the consice information about them without a huge description.
Thank you
The attached document is a Guide for Chief programmers. The document was written for "Software Architecture and Engineering" course at Harvard University. This year the course is applying FDD to implement the course project. The document describes the typical activities that Chief Programmers perform during FDD iteration.
For the first time our company is developing with FDD. The software should be tested by the internal software test team, because there is no real customer. The test team is used to system testing in the classical way. The plan is to develop the software in iterations, but we are not sure how we should plan the system tests.
Does somebody has a suggestion on how we should plan the system tests?
Hi,
please try to find out with me how I can merge both the Business Domain Object Model and the J2EE Technology so that at the end I will obtain a full fledged Application that fullfill the domain model and the requirements.
I would like to take the case study example in Mark Cade's SCEA book (p.158) for this discussion. The case study describes a company that has requirements very similar to Amazon.com.
First of all we get a number of use cases and a business domain object model (BDOM) as below from a business analyst:
Cutting content seems to be the prevalent way of meeting deadlines in projects that are running late. But why waste effort and time on things that most likely, will go at the first sign of trouble? Why don’t make the decisions about what is important and what is not up-front, and only start work on the latter if we have the necessary time to do it?
By combining critical chain and incremental development, we can create a plan and execute projects, which guaranties, with a set probability, the delivery of an agreed subset of the total functionality by a stipulated date.
You are the project manager of a large project, testing is uncovering faults, trouble reports (TRs) are starting to pileup, the release date is coming soon. Are they going to be fixed on time? What could you do to help? Are there any bottlenecks? Where should you assign more resources?
Sounds familiar? Have you been there? This article will explain how could you answer these questions by using an old method called Line of Balance in a new way.
