you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 years ago (1 child)

I don't know man. Nothing in the Agile Manifesto talks about not focusing on one project.

In addition, I think most people (and studies) would agree that "focus" is key to building almost anything of quality. Not flittering about working on shiny pennies of the day. I mean, a key tenant of sprints is "Don't interrupt the sprint". The whole concept is about letting developers focus.

Agree to disagree I guess.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago

    Might wanna read it again, it's right there :)

    The best architectures, requirements, and designs emerge from self-organizing teams.

    It's an incredibly critical part companies love to completely ignore.

    If you assign devs to teams and lock em down, you've violated a core principle

    And it's a key role in being able to achieve these two:

    Agile processes promote sustainable development.

    And

    The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

    This is talked about at length by the likes of Fowler, who talk about how locking devs down us a super fast way to kill sustainable development. It burns devs out fast as hell.

    Note that it's careful not to say on the same project

  • source
  • parent