Re:How do you communicate if you won't hit an estimate?
by ThomaszKrueger on Monday October 20, 2014 @01:58PM
(#8483517)
How do you account for the hours you spend "communicating", and will there be hours left for real work?
[ Parent
| on HN ]
Re:How do you communicate if you won't hit an estimate?
by munirusman on Monday October 20, 2014 @03:36PM
(#8484039)
It doesn't take much time if we use right tools. I've found Asana really good for task management with your team. As software dev, all you have to do is to tick completed tasks or write short comment if you are missing deadline for an individual tasks.
Also, committing code multiple times a day with meaningful comments also helps.
Re:How do you communicate if you won't hit an estimate?
by anthonye on Monday October 20, 2014 @04:06PM
(#8484198)
Any advice for easily communicating with non-technical clients who wouldn't use technical tools?
Re:How do you communicate if you won't hit an estimate?
by munirusman on Tuesday October 21, 2014 @02:11PM
(#8488807)
I have faced many non-technical clients in past and trust me it's not easy. The best thing I could do is to double (sometimes triple) the original estimated timelines.
Make separate milestones for QA and UAT rounds.
Breaking the project in very small but presentable milestones helps in keeping non-technical clients updated and happy.