Wednesday, April 8, 2009
Tuesday, April 7, 2009
Stir Trek
Stir Trek is an opportunity to learn about the key announcements from the Mix 09 conference, at a location that is a little closer to home, and in the comfort of a movie theater. There will be 10 sessions, in two tracks, so you’ll be able to pick the content that interests you the most. In addition, the day will include lunch, a raffle with some significant prizes, and a private screening of the new Star Trek movie, which opens in theaters the day of this event.
Friday, April 3, 2009
Microsoft ArcReady
--------------------------------------------------------------
Architecting for the Client Tier
The client (or presentation) tier of our applications is taking on an increasingly important role. Users are expecting more compelling user interfaces, but they also want more functionality from their applications. In this ArcReady we examine how to design and deliver well architected client applications that will be easy to maintain and extend.
Session 1: Trends and Patterns on the Client Tier
In our first session we will take a vendor and platform neutral look at some of the trends and emerging technologies that can be used on the client tier. We will look at techniques like Mashups, technologies like Natural User Interfaces (NUI) and the increasing importance of the mobile platform. We will also look at some common patterns that can be used in the architecture of the client tier.
Session 2: Applying Microsoft Technology on the Client Tier
In our second session we will take some look at how we can use Microsoft technologies to create well architected and compelling client applications. We will look at technologies like Silverlight and WPF that can be used to create compelling clients. We will also look at technologies that can be used to make your applications more extensible for future development. We will also examine some architectural guidance developed by the Microsoft Patterns and Practices group.
WHAT IS ARCREADY?
· A forum for aspiring and practicing architects to discuss industry trends
· An overview of Microsoft’s roadmap as it relates to software architecture
· A mechanism to solicit your feedback
· An opportunity to showcase the work you do!
WHO SHOULD ATTEND?
Architects and Senior Developers who are interested in becoming an architect.
WHERE ARE THE EVENTS?
Events are held in 16 cities across Central Region. To register for this event, please visit http://www.arcready.com/.
Location/Registration
Cleveland, OH
4/30/2009
9:00am – 11:45am
Columbus, OH
5/12/2009
9:00am – 11:45am
Mason, OH
5/14/2009
9:00am – 11:45am
Southfield, MI
5/20/2009
9:00am – 11:45am
Nashville, TN
6/11/2009
9:00am – 11:45am
Knoxville, TN
6/12/2009
9:00am – 11:45am
Cincinnati SPIN
Thursday, March 12, 2009
Lean Software Development
I recently posted a synopsis of Chapter 1 of Lean Software Development: An Agile Toolkit . I’ve kept up with my reading, but have failed to provide a synopsis of Chapters 2 and 3. In this post, I’m going to cover both in order to get caught up.
Chapter 2
This chapter is titled “Amplify Learning” and focuses on learning and experimentation as a key success factor of Agile Development. It starts with some great insight as to how software development differs from manufacturing. There have been numerous attempts at applying lean production practices to software development, most of them unsuccessful. There is a significant difference between the two. Development is more closely related to the creation of a recipe, where learning and experimentation are encouraged and rewarded. Production is simply following that recipe in the most efficient manner possible. The authors provide an excellent comparison between the two.
| Development | Production |
| Designs the recipe | Produces the dish |
|
|
|
|
|
|
Chapter 3
This chapter is titled “Decide as Late as Possible” and focuses on delaying design decision as long as possible. The focus in Lean development emphasizes producing a design that is supportive of the changes that are inevitable. This is accomplished through iterations, with each part of the system being designed just enough to support the requirements for that iteration. This forces the design to be modular and adaptive to change as it will be modified in the next iteration. Once the system is released to production, the support lifecycle will be greatly enhanced as well.
One of the key concepts is delaying decisions until the last responsible moment (defined by the Lean Construction Institute), which is the moment at which failing to make a decision eliminates an important alternative. Delaying decisions is difficult for most people, it's hard work. This is a key concept in the Agile world. However, delaying decisions past the last responsible moment will lead to decisions made by default which is more damaging than making the wrong decision early.
I will try to provide a more complete synopsis of the next few chapters, but wanted to get caught up with these. Stay agile!
Thursday, March 5, 2009
Planning Poker® Design Contest
Submissions must be received by May 15, 2009. They will select the winning idea and give the winner a $500 gift card from Visa and twenty-four decks of Planning Poker® cards with the new design.
Read more and enter here:
http://www.mountaingoatsoftware.com/contest
