The below are only the points. Read the original article in [www.littletutorials.com]. Really awesome. In fact, the author of this article inspired me to restart my knowledge sharing activity and started writing few thing in the web. Sec-1:Set yourself up for success Define early on what success means for you, the team and the business Believe in the project: idea, architecture, time, team Understand the domain, the business requirements and the technical challenges Know your team: strengths, weaknesses, ambitions and personalities Have a plan as a result of a planning activity Be part in the design of everything Get your hands dirty and code8. Act as a communication proxy for your team Make sure everybody understands the big picture: their work has implications Fight for architecture and design consistency Know the status of everybody’s work and detect slippage Record technical debt if you need shortcuts but try to maintain architectural integrity; report the debt Use the process that...
Every action of ours will always have a reaction!