but putting in too much effort into a project can be a problem.
However, what about the case of putting too little effort into the project.
not meeting deadlines because of it.
developers to do development work, because they're so focused on doing other things.
focuses on working software over comprehensive documentation.
that brings about its own problems.
not working on important, high-value things.
time building presentations, reports, and documentation, instead of developing code.
a developer must fully analyze its potential before going forward.
It's a lot like analysis paralysis but at an organizational level.
presentations would be enough to create a basic product prototype.
a bonus of having working software off of which successive products can be built.
then the prototype serves as a lesson learned.
A lesson that can be carried on towards future projects.
weekly meetings using a slideshow format.
She does this so that everyone's ideas can be expressed accurately and clearly.
What is the problem with Reyhan's expectations here?
The developers time, would be better spent developing code.
Nothing, this is a good communication practice.
Software developers are bad at making slideshows.
Software developers have only a finite amount of time to work on projects.
then they'll have less time to create the actual product.
managed to complete all their work.
Is that enough to say that the project was successful?
overtime towards the end of the project to meet deadlines.
This anti-pattern is referred to as a Fire Drill.
then all of a sudden need to make a big push toward the end.
the impact of a developers themselves wasting time.
It can also occur when expectations are not properly set with the client.
in favor of getting the product out the door quickly.
since there wasn't enough time to build the product properly.
Fire drills often lead to another anti-pattern, called Heroics.
nearly superhuman technical skills to get the project done.
even outside of the big push at the end.
early in your project and follow an agile software development practice.
that give your developers the structure they need to get things done on time.
their development teams are equally motivated to complete the project.
Which of the following describes heroics as it happens in software development?
Often relies on one person to solve their problems.
Contains someone who has been knighted.
The answer is B, heroics in software development is not a good thing.
What happens when the development team and management are at odds?
to believe in the work they're doing?
This is called a Death March.
failure, but everyone continues to build a project anyway, out of obligation.
Imagine the terrible consequences of this.
are management forcing the project on a development team for financial reasons.
Or management might be stubborn and in denial of the inevitable failure.
can pretty much assume that the product isn't going to be the best it can be.
Developer morale in Death Marches is low and the product quality suffers for it.