In every non individual project we have an aspect of people and collaboration. Humans are emotional creatures, therefore we have to care about each other. In all projects I'm in, I'm bringing into the live the following rules:
- Rule number 1: reduce stress.
- Rule number 2: communicate well.
- Rule number 3: be responsible.
I encourage to follow the Agile workflow: http://bit.ly/agile-workflow where I discuss the whole product development process.
Another methodology I follow, and fully recommend is the Workflow.After years of experience running companies, and tons of blog posts and books, we've concluded that, despite a rich body of organizational theory, the practice of organizations is a big mess. Many random concepts, ideas, tips, tricks, heuristics, "systems," etc. Lots of trauma, power struggle, failed expectations, unaccountability. Lots of "Google does this" and "Netflix does that." Lots of deference to Silicon Valley's dominant narratives and ideologies. But what's often lacking is a meaningful yet practical way to reason from first principles about organizational structure and accountability.
We were introduced to a simple language called "Workflow" by Melissa Angeli and Laura McKinney of Jacquarden Consulting. Laura and Melissa were previously the CEO and Head of People for Galois (respectively), a successful R&D company in the US with an acclaimed organizational design, known as the Collaborative Web (original source). The paper describes common dysfunctions in management and leadership and how the collaborative web structure resolves them. It is well worth reading.