Danno Ferrin suggests applying principles used in magic for a better user experience: Consider the Stage and the Audience, Practice, Overcome Objections Before They Arise, Patter and Showmanship, Sleight of Hand, Direction, Simulation, Dissimulation, Anticipation.
Microsoft has put together a number of resources for Visual Studio developers, containing principles, practices and guidelines for Agile development. These resources are condensed articles written by influential Agile leaders -Jeff Sutherland, Ken Schwaber, David Star, Mitch Lacey, David J. Anderson - containing the essence of several Agile methodologies and being usable by any software dev team.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
A recent post by Joshua Kerievsky contrasting Lean Startup with Agile approaches resonated with some commentators and raised the ire of others. Do Lean Startup principles replace and supersede Agile approaches or are they complementary.
Ivo Manolov, a Principal Software Manager and former WPF SDET Manager at Microsoft, has written a short post on project management principles and techniques useful for those who want to be a project manager in their organization or want to improve their management skills.
Security concerns are the number one barrier to cloud services adoption. How do we evaluate a vendor's solution? What is an optimal security architecture? What are consumer versus provider responsibilities? What are industry standard patterns in this regard? This article answers some of these questions based on first hand experience dealing with large scale cloud adoption.
In this article, Jimmy Nilsson describes an architectural style that he has observed slowly growing in popularity over the last few years, a style that he calls Chunk Cloud Computing.
Frank Buschmann’s secrets: User Tasks-based Design, Be Minimalist, Ensure Visibility of Domain Concepts, Use Uncertainty as a Driver, Design Between Things, Check Assumptions, Eat Your Own Dog Food.
Rick Simmons presents a launch process meant to introduce a team to Kanban in two days, focusing on the core concepts and techniques, and by setting the team on an improvement path.
Adrian Colyer presents along with a Spring team the key principles guiding SpringSource evolution over time, what has happened from the previous SpringOne event, and where SpringSource is headed to.
Justin Sheehy explains why a paradigm shift is necessary when dealing with large concurrent distributed systems and what are some of their requirements: no global state is shared, ACID no longer works but rather BASE and CAP, getting rid of RPC and using protocols over APIs instead, prepare for failure, degradation, understanding the harvest-yield balance, and using measurement.
