| 100% agree with you on delivering small bits at a time. That's where I came from. However this time round, contracts are signed, everything listed in the functional spec must be delivered by end of 3 months, non amendable. We still do weekly progress update and demo. What I failed to convey to my team is that qualities are important too. Instead, I've got many hardcoded things from them at almost the end of the project, no test, no nothing. Stakeholders do not understand that quality software needs time, yet they continue to stress on quality while sticking to the timeline. I figure I'll need to educate them better next time. > Upfront documentation isn't necessarily the best way of getting knowledge accross(Although it should be used). The best is collabarating, pair programming with your team etc Agreed! That's what we did, using PRs. I reckon that every developer should know how to write a good commit, breaking or squashing commits into meaningful pieces. that'll make PR easier to read. > I don't know what your situation was, but these days setting up ci/cd pipeline to a staging/prod slot for a small project is fairly quick... Well, let's just say I learn it too late while tangling with other issues. Also I find dev in the team underappreciated CI/CD, people really don't write tests too. More education planning in plan. Thanks again for your time. |