Rules and Guidelines
Want to participate in the discussions? Please read our Community Rules and Guidelines. Need some help? Visit Support and Answers.

  • State Not Answered
  • Replies 7 replies
  • Subscribers 15 subscribers
  • Views 1237 views
  • Users 0 members are here
Options
You may also be interested in

How does the choice of software engineering methodology impact the adaptability and responsiveness of a development team in the face of changing project requirements?

Mustafa Ozdeser

The choice of software engineering methodology directly impacts how effectively a development team can adapt to changing project requirements. Agile methodologies, such as Scrum or Kanban, enable quick adjustments and continuous collaboration, enhancing adaptability and responsiveness. Conversely, traditional methodologies like Waterfall may hinder the team's ability to respond promptly to evolving project needs, potentially causing delays or inefficiencies.

Parents
  • 0

    I have heard a lot of push back against Scrum recently, saying that it makes things worse for the engineers.

    1. It takes the concept of "agile" and dumps a load of process on top of it.  This keeps managers happy, and the engineers get fed up with the endless meetings.
    2. The "customer" is never actually the customer.  They don't want to tie up one of their staff in endless meetings with their suppliers.  So the "customer" is actually a manager.  And the manager already has a plan saying what tasks will be done when, because that's what managers do.
    3. The whole thing turns into an endless treadmill for the engineers.  At the beginning of the sprint, you're given a task and a limited time to complete it.  Fail to complete it on time, and management will notice.  Do well, and they will give you a bigger task next time.  It ends up a way to keep loading more work on the engineers, while telling them that they are being "agile".
Reply
  • 0

    I have heard a lot of push back against Scrum recently, saying that it makes things worse for the engineers.

    1. It takes the concept of "agile" and dumps a load of process on top of it.  This keeps managers happy, and the engineers get fed up with the endless meetings.
    2. The "customer" is never actually the customer.  They don't want to tie up one of their staff in endless meetings with their suppliers.  So the "customer" is actually a manager.  And the manager already has a plan saying what tasks will be done when, because that's what managers do.
    3. The whole thing turns into an endless treadmill for the engineers.  At the beginning of the sprint, you're given a task and a limited time to complete it.  Fail to complete it on time, and management will notice.  Do well, and they will give you a bigger task next time.  It ends up a way to keep loading more work on the engineers, while telling them that they are being "agile".
Children
No Data

Join us to get the best from IET EngX.

Joining EngX lets you personalise your experience so you stay up to date on the topics that interest you, plus you’ll be able to make connections who are looking to collaborate, exchange ideas and more.

Join us Not now

Community Rules & Guidelines