Skip to main content

One way that I have found that works is to have the developer put together a presentation, and then present the results to the team, who will undoubtablyundoubtedly ask questions about how things work, where things are etc. This works because no one wants to end up going to a meeting unprepared and encourages communication, rather than have it be a solitary project.

-Ralph Winters

One way that I have found that works is to have the developer put together a presentation, and then present the results to the team, who will undoubtably ask questions about how things work, where things are etc. This works because no one wants to end up going to a meeting unprepared and encourages communication, rather than have it be a solitary project.

-Ralph Winters

One way that I have found that works is to have the developer put together a presentation, and then present the results to the team, who will undoubtedly ask questions about how things work, where things are etc. This works because no one wants to end up going to a meeting unprepared and encourages communication, rather than have it be a solitary project.

Source Link

One way that I have found that works is to have the developer put together a presentation, and then present the results to the team, who will undoubtably ask questions about how things work, where things are etc. This works because no one wants to end up going to a meeting unprepared and encourages communication, rather than have it be a solitary project.

-Ralph Winters