Comments on: Round-up of Processes, Methodologies, & Best Practices http://refactr.com/blog/2006/11/round-up-of-processes-methodologies-best-practices/ informs on and evangelizes best practices of using <a href="http://refactr.com/the-agile-manifesto/">agile methods</a> when designing and developing what are currently being called “Web 2.0” products and applications. Tue, 15 May 2012 14:51:32 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Ben http://refactr.com/blog/2006/11/round-up-of-processes-methodologies-best-practices/comment-page-1/#comment-165 Ben Tue, 07 Nov 2006 02:16:40 +0000 http://refactr.com/2006/11/06/round-up-of-processes-methodologies-best-practices/#comment-165 Jesse you hit on some good ones, and there are many on the list. Here are three additional refactr faves: <ul> <li><a rel="nofollow" href="http://pairprogramming.com/" rel="nofollow">Pair Programming</a> - We use this a lot here at work. More interesting for me is how we sometimes pair a designer and a developer for work on more of the client side work.</li> <li><a rel="nofollow" href="http://c2.com/cgi/wiki/wiki?HistoryOfIterative" rel="nofollow">Iterative and Incremental Development</a> - One of the most important things we do is release new code each week. This allows for a great deal of flexibility and responsiveness to the needs of the client. We can essentially change course each and every week; accounting for shifts in focus and priorities.</li> <li><a rel="nofollow" href="http://c2.com/cgi/wiki/wiki?HistoryOfIterative" rel="nofollow">KISS principle (Keep It Simple, Stupid)</a> - Whenever I am trying to solve an interface problem, perhaps deciding between two or more options I know I can rarely go wrong by selecting the simplest solution.</li> </ul> Great list! Jesse you hit on some good ones, and there are many on the list. Here are three additional refactr faves:

  • Pair Programming – We use this a lot here at work. More interesting for me is how we sometimes pair a designer and a developer for work on more of the client side work.
  • Iterative and Incremental Development – One of the most important things we do is release new code each week. This allows for a great deal of flexibility and responsiveness to the needs of the client. We can essentially change course each and every week; accounting for shifts in focus and priorities.
  • KISS principle (Keep It Simple, Stupid) – Whenever I am trying to solve an interface problem, perhaps deciding between two or more options I know I can rarely go wrong by selecting the simplest solution.

Great list!

]]>