January 27th, 2009

Silverlight team integration

Working with Silverlight, by Gavin Wignall.

Traditionally designers and developers have always been treated as very different people. Developers known for being analytical, precise, literal and logical often being seated in a group away from the imaginative, creative and conceptual group of designers. When these two groups work on a project together there is often process put in place to attempt to hand a project over from design to development with little interaction once the pass has been made

With internet applications getting richer every day, the need for user experience and quality assurance becomes more an important oversight. Not only do designers and developers need to be more aware of what the other actually does, but each party is having to help the other realize the limits and possibilities of new mediums available to them.

Microsoft Silverlight is one of these new mediums and plugs straight into Microsoft’s .NET framework, allowing deep functional purpose to lie behind rich user experience.

However, with risk of sounding like a super hero, with this greater power becomes greater responsibility to retain quality and manage user expectation. Sitting designers and developers side by side can help projects in many ways. When a new project is started it is important to assess and potentially relocate the team to ensure maximum communication can be obtained between designers and developers.

Help train each other

Both sides need to pick up new software and new ways of thinking that the other side takes for granted. For example, designers will need to pick up Source control and understand naming convention where as developers will need to understand animation through storyboards and dynamically through coding.


Understanding your counterparts process, potential and limitations will allow both parties to design and develop applications realistically and on target.

Problem solving

Remember that each party has a good mix of opposing skills/way of thinking. Your counterpart may not always give you a solution to a problem, but they will often give you a good outside the box angle that can often lead to or spark off a new idea to your trouble.

Work Flow

The delay of a project going back and forth between design and development is minimized.

Team work

Getting to know your counterpart will help you understand frustrations on both sides better and allow for a more enjoyable work environment and hopefully a lot less finger pointing.

Back Top

Responses to “Silverlight team integration”

  1. Fantastic – Thanks for the tip :-)

  2. Not really a true indication of collaborative work space integration, may be the same model we use but i think you have not put it across properly

    Jeremy Irvine at January 28, 2009 5:48 pm
  3. Thanks for your feedback Jeremy!

    The driving point of my post is to get across the importance of of taking that first step of breaking down walls between design and developer teams.

    Indeed there are many additional factors and good practices to adhere to, to perfect a true collaborative work space, happy to discuss this further and swap ideas – mail me ;)

  4. Appreciate this. Really educational post.

  1. goudie (,March 5, 2010)

    [...] not be published) (required) Website. Powered by WordPress. All Content (C) Lesley C Of Sh00gar. …Silverlight team integration Silverlight BuzzGavin Wignall Blogs about Silverlight tutorials and examples … Milford Goudie at January 13, 2010 [...]

Leave a Reply

Back Top