The tendency was often to put that bug Telemarketing List at the top of our to-do list and fix it as soon as possible – especially if it was an investor who pointed it out to us. A better approach is this: if a bug is reported, create a ticket for it. Then it is Telemarketing List possible that a developer picks it up during the cool-down. Is this bug not being picked up by a developer? Then it can always be pitched for the upcoming cycle. But the bug will not be Telemarketing List randomly added to the current cycle.
The exception here is if the bug kills the Telemarketing List product. For example, it causes an app to crash on a popular phone type. In this case, you should of course stop all work and fix the bug as soon as possible. Deeper into the matter Of course, this topic Telemarketing List can be discussed in a lot more detail. If you're interested in this, you can read Basecamp's free book Shape Up. Basecamp explains their methodology in extreme Telemarketing List detail. I would think of their book as a buffet.
Choose what applies to your Telemarketing List organization and ignore the rest. If you don't like sushi, don't eat the sushi. Ultimately, the 6-week cycle has led to the following benefits for us: Developers became happier The quality of the Telemarketing List product got better And projects no longer dragged on indefinitely Do you have any questions or comments about the 6-week cycle, or do you think your team has an approach that works Telemarketing List better? Please leave a message below.