|
|
|
|
|
|
by alexgvozden
2913 days ago
|
|
|
I see many people see this as backwards and top to bottom approach while I consider it utmost bottom to top approach in all the teams I worked most successful were ones that insisted on writing wiki / readme pages for each feature and task... why? 1) project manager (person knowing why we're building) has to do fair amount of explaining to the developer
2) it's easy to verify that developer understands what he/she needs to develop
3) everyone else in the team can easily update themselves my template was something like this 1) what has to be built
2) for whom - who is the typical user and scenario
3) who will built it and which branch on git
4) what app parts will be changed
5) any information related to deployment (database changes and similar) doing it upfront meant a lot to the team, discussions and clarity... I would just call this more Wiki development then readme :) |
|
|