- After project is awarded or confirmed, system analyst or programmer could start to research, learn and test core technology that could be used
- Basic coding could start if standard framework such as Spring or Spring Boot is used
- Basic function could be developed first, e.g. system code/ parameters, account, logging, audit trail
- Pilot test core code before implementation to avoid side effect on project such as performance
- Reuse features or functions developed in other projects, if possible, e.g. microservice
- Resue if possible existing database structure or some configuration file
- Multiple projects need to develop same function, assign same person(s) to work on it
- Need architect to check overall technical issue but well communicate with each team leader
- Assign task only after checking with staff in person their strengthen, weakness and preference
- Redistribute task among staff to speed up progress when necessary but obtain their consent first
- Encourage staff of different project to share knowledge, seek for advice in company portal/ forum
- Share project experience after completion by hosting sharing/ demo session every month/quarter
- Promote on schedule mindset and OT only when really necessary
- Review issues with staff after passing 1/4 or 1/3 schedule time
- Simplify existing documentation, customize and adapt to reuse on different projects
For more details, please refer to the book Project Planning or System Development Instant Reference. It is available in ebook or print format in English, Japanese, Traditional and Simplified Chinese.
No responses yet