{"id":8,"date":"2010-02-22T18:07:13","date_gmt":"2010-02-22T22:07:13","guid":{"rendered":"http:\/\/hotsoft.carleton.ca\/hotsoft\/?page_id=8"},"modified":"2015-07-01T13:08:26","modified_gmt":"2015-07-01T17:08:26","slug":"agile","status":"publish","type":"page","link":"https:\/\/hotsoft.carleton.ca\/hotsoft\/projects\/agile\/","title":{"rendered":"Agile Software Development"},"content":{"rendered":"\n\n\n
\"untitled2.png\"<\/td>\n\"untitled1.png\"<\/td>\n\"untitled4.png\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Agile processes are one of the most exciting things to happen in software development in the last decade.\u00a0 There were a number of early beginnings, and these led to the articulation of several different processes. Perhaps the best known are Scrum<\/a>, and Extreme Programming (XP) <\/a>which despite its name has a wider and deeper agenda than just programming.\u00a0 When the creators of the various new approaches got together, they found a lot to agree on, summarized in their 2001 Manifesto for Agile Software Development<\/a>:<\/p>\n

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: <\/span>
\n<\/span><\/em><\/p>\n

-Individuals and interactions over processes and tools<\/span><\/em>
\n -Working software over comprehensive documentation<\/span><\/em>
\n -Customer collaboration over contract negotiation<\/span><\/em>
\n -Responding to change over following a plan<\/span>
\n<\/em><\/p><\/blockquote>\n

That is, while there is value in the items on the right, we value the items on the left more.<\/em><\/p><\/blockquote>\n

Agile processes are still new, and there is much to be done in determining what works well and when. In particular, there is a need to explore the relationship between agile processes, user interaction, teamwork, and value.\u00a0 These are the elements in the “human side of agile development”: the focus of our research work.
\nFaculty<\/strong><\/span><\/p>\n