Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Activity Profile

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Emergent Architecture

Date: May 16, 2011 from 3:00PM to 4:15PM
Day 1
DPR308
Speakers: Richard Hundhausen
Avg Rating: 5

(1)
5,552 Views
2 Comments
reddit

Tweet

format
< > embed
+ queue

Sign In first to access your queue.
Close

Sorry, video was not added to the queue, an error occurred. Please Contact Us and let us know.
Close

Embed code for this video

Copy the code above to embed our video on your website/blog.

Video format

Option selected may change based on video formats available and browser capability.

Auto
Use our suggested format for this video.
Smooth Streaming
Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth. Silverlight 5 required
Progressive
Traditional buffered video format. Silverlight 5 required
HTML5
For browsers that support H.264 MP4 or WebM video playback such as:
IE9+, Firefox 4+, Chrome 5+, or Safari 4+.
Flash
For browsers that have the Adobe Flash Player plugin installed.

Download

Right click “Save as…”

MP4 (iPod, Zune HD)
Mid Quality WMV (Lo-band, Mobile)
High Quality WMV (PC, Xbox, MCE)

Agile software development emphasizes that some increment of business value be delivered every iteration. How can this happen when your iterations are two weeks in length and you estimate it will take you two months just to design the database and the access layers? The answer is to think in slices,not layers. In this session,learn how to implement enough of each layer,including the database,to solve that iteration’s problems and provide value to the business. As we use good design principles,engineering practices,and tools,the architecture will emerge. By avoiding big design up front,we’ll skip the wasted coding and brainpower on the low priority user stories. The requirements would have changed before we got to them anyway. If you are thinking this is very difficult,then just remember this FAQ: Does it take a smart person to be an Agile developer? No,it takes a smart person to write software!