Entradas del foro

jessy jessy
06 abr 2022
In Discusiones generales
So when you start the project, you will be Whatsapp number database faced with few or no surprises. That way, the 6 weeks of the cycle are about implementation and execution – not planning. Protect your developers To make sure you don't go past six Whatsapp number database weeks, you need to protect your tech team. You do this by saying no to 'quick' requests from, for example, an account manager. If a non-technical person thinks "this can't be more than 5 minutes of work, can it?", you often see a Whatsapp number database that the actual duration is closer to 3 hours. And then there are the costs Whatsapp number database associated with task switching. If a developer suddenly has to take up another project, this will disrupt his flow. Developers don't cut their days into small chunks like a marketer or sales manager does: they need long Whatsapp number database consecutive days of full concentration. The moral of the story: always protect your developers' time. What to do with bugs in the 6-week cycle? People often think that a bug is a good reason for the Whatsapp number database shut down projects and not resume until the bug has been resolved. But all software has bugs. There's nothing special about it. With us, it sometimes happened that we discovered a bug that had been there for months. The tendency was often to put that bug at the top of our to-do list and fix it as soon as possible – especially if it was an investor whose Whatsapp number database pointed it out to us. A better approach is this: if a bug is reported, create a ticket for it. Then it is possible that a developer picks it up during the cool-down. Is this bug not Whatsapp number database being picked up by a developer?
0
0
4
J
jessy jessy

jessy jessy

Más opciones