Construction architectural design has been an integral part of mankind life for almost all its being. It went through several revolutions based on the needs and requirements of different eras. With the enhancement in technology and machinery in the last few decades the competition in this industry have become more important every year. Customers as well as construction development usually don't know what they want at the start of the project. Also by the end of a large project the feedback might change all the work that might waste many of the resources time and effort. Specially in larger cities with more investment on the look of the buildings as well as the interior architectural points, the requirements nature change every year, new material, shapes, and designs emerge every month.

This might remind you of another product of your expertise, yes it is software. Finding out about Agile and its influence on software world and the similarities we decided to apply some of the values and principles as they fit to architectural design. However, we considered the major differences between the two such as lower rate of evolution, less diversity of the tools, etc.

In this session, we will go through my experience in applying agility to some of the project in Los Angeles area. We will discuss the similarities and differences between the two industries, and how we took advantages of the experiences in the software industry.

 
 

Outline/Structure of the Case Study

Definitions and terminologies

History of Architecture

Case study description

Similarities and differences with IT

Conclusion

Learning Outcome

understand agile values and principles deeply

learn about application of agile in architectural design

gain vision on cause and effect of Agile

Target Audience

Agilists interested applying values and principles in industries otehr than IT

schedule Submitted 1 month ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  1 month ago
    reply Reply

    I think the submission could be improved by:

    • It's not clear who would benefit from attending this session. It's unlikely that there will be architects unfamiliar with Agile at the conference
    • The submission needs to spell out the target audience and what they will gain (i.e., "be able to do," not just "understand") from attending.