• Must have a history of working effectively in a cross-functional team environment.
• Must demonstrate a history of a high degree of self-motivation and initiative.
• Must be able to prioritize, plan work to accomplish goals, and schedule tasks to meet deadlines
• Ability to adapt and respond positively and effectively to change, delay, and/or shifting priorities and goals

Technical Skill Requirements:

With software focus vs. Firmware background

• BS and/or MS in Computer Science or equivelant
• At least 5-years in software industry
• Passion of solving problems by software and programming
• Experienced with networking protocols
• Solid unit-test and/or automated testing experience
• Experience with front-end and back-end systems
• Design patterns a must
• Database experience required
• Scripting skills are also nice
• With strong object-oriented design and development skill
• Emphasis on Windows form (instead of web application) and new view model design pattern
• Preferred with C++ or Java background (instead of e.g. Visual Basic or VB.NET)
• Knows how to debug and parse log information
• Experienced with Subversion, or at least one version-control tool
• Experienced with XML and SQL
• Ideally with experience of multi-threading programming
• Ideally with experience of WPF or Silverlight
• Ideally with C#.NET for HTTP or web

Personality and Attitudes

• Passion for perfection in design and programming
• Track record of teamwork experience in previous projects
• Had failure experience in previous project
• Had good and bad experience with test team
• Fit into a fast-paced group

• Must have a history of working effectively in a cross-functional team environment.
• Must demonstrate a history of a high degree of self-motivation and initiative.
• Must be able to prioritize, plan work to accomplish goals, and schedule tasks to meet deadlines
• Ability to adapt and respond positively and effectively to change, delay, and/or shifting priorities and goals

Technical and Other Skills

• Ability to develop software based on the Microsoft Windows(r) platforms using Visual Studio 2010
• Knowledge and proficiency in the following areas:
• .NET Framework 4.0, C#, SQL. Linux, Telephony, (Perl scripting would be useful also).
• Excellent written and verbal communication skills.
• Work within the standard product development design control procedures for designs, development, and  testing of software-based products and systems.
• Perform the work necessary to resolve complex issues within existing products and portions of new designs.
• Propose design changes and resolve known issues within emerging and existing products

• Must have a history of working effectively in a cross-functional team environment.
• Must demonstrate a history of a high degree of self-motivation and initiative.
• Must be able to prioritize, plan work to accomplish goals, and schedule tasks to meet deadlines
• Ability to adapt and respond positively and effectively to change, delay, and/or shifting priorities and goals

Technical Skill Requirements:

• WPF
• XAML
• C#
• UX User Experience
• UI User Interface
• Microsoft Expression Blend 4 and maybe Designer 4
• Strong Understanding of data states
• Use of Dynamic and static Resources
• Also the use of Behaviors and Triggers
• Use of SVN a plus or some type of version control
• Visual Studio 2010
• Know how to use most of the Adobe Suite
• PhotoShop 5
• Illustrator 5

BIG PLUSES:

• Flash is a plus since it’s a good animation base knowledge for Object orientated programming and also time line base animations
• .Net is a Plus
• NUI Natural User Interface
• DGI Designing Gestural Interface

Mike Griffiths outlines the Value Stream Mapping principles for the new PMI-ACP exam.

Andrew Clifford has an excellent post on Bootstrapping.

Steven Roock provides 5 tips for impediment resolution with Scrum.

Dan Naden talks about Agile not being a game of perfect.

Judy Umlas discusses the 7 principles of acknowledgement for a project’s culture.

Finally, Conrado Morlan talks about adding Gen Y to your projects.  Many of you know that I believe one of the major shifts in our economy is this generation and harnessing their incredible creativity and differing work style.  This is a solid post!

Ty Kiisel thinks we shouldn’t call the people on our project “resources.”  What do you think?

The Agile Manifesto says we should have working software over comprehensive documents.  While we agree with this, one documentation expert shows how documentation can not only be useful but critical.

Lee Cunningham talks about Agile Transformation and possible failure.  The point of agile is to fail quickly and often so you build the right things that have real value.  Why would you possibly give up on that?  What do you think?

Shouldn’t every manager be a center of excellence?  Saira Karim suggests we combine PMOs and COEs?  What do you think?

We agree with Lynda Bourne  that happy project manages are productive project managers.  What about you?