Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thank you for the answer, I also believe evolutionary processes are the most successful. But are there any useful quantitative measures for "tuning a process" or is it based entirely on "feel" of the developers and stakeholders? Commented Apr 28, 2012 at 14:37
  • @GarrettHall It's less "feel" and more about observation. As the project progresses, you review the process frequently to identify causes for inefficiency. If the team notes that missing information causes delays, find out why the information isn't available and fix it. If the team has a lot of long meetings, either streamline the meetings, or remove them altogether. If customer interferes with development, manage the relationship with the customer. If tasks take too long to complete, break the tasks down. If something is difficult to make more efficient however, you may need to experiment. Commented Apr 28, 2012 at 23:40