4 ms·

How about: Don't follow a fixed, predefined process but find the one that works for your specific situation and adapt it when needed.

nine_k 4y ago
Sounds like a lot of work. Starting it from scratch would be a project in itself. So some assortment of reasonable starting points, with their pros and cons described, would be valuable.
- valenterry 4y ago
  Why so? No one forbids you to pick a process and/or tools that come close to the perfect process and then change them as necessary. You don't have to reinvent the wheels. You can use Scrum, Kanban, ... as starting points. Just don't implement them mindlessly like most companies do.
  - cassianoleal 4y ago
    "Individuals and interactions over processes and tools" "Responding to change over following a plan" These are 2 of the 4 tenets in the manifesto for agile development [0]. They go on by saying: "That is, while there is value in the items on the right, we value the items on the left more." Essentially, choose tools. Follow processes. Periodically and permanently reevaluate. If following the plan creates an impediment to interactions, or makes the people dissatisfied, respond to these changes. Rinse and repeat. [0] https://agilemanifesto.org/ https://agilemanifesto.org/
andrewflnr 4y ago
That sounds good, sort of a mindset of flexing and changing direction as you move forward. You might call it... agility.
pempem 4y ago
This is the agile suggestion. A previous commenter had it right imho. Its not that the approach isn't working, its that it has been co-opted by management and requires separation to actually succeed. Another note would be that agile itself says: - non team members shouldn't be at stand ups etc. - points shouldn't be used for evaluation of performance (good luck with that) - if management joins anything other than the demo, they should not speak during the meeting (I've had some success here but also always been labeled a curiosity when I push management to be silent)

nine_k 4y ago

Sounds like a lot of work. Starting it from scratch would be a project in itself. So some assortment of reasonable starting points, with their pros and cons described, would be valuable.

valenterry 4y ago
Why so? No one forbids you to pick a process and/or tools that come close to the perfect process and then change them as necessary. You don't have to reinvent the wheels. You can use Scrum, Kanban, ... as starting points. Just don't implement them mindlessly like most companies do.
- cassianoleal 4y ago
  "Individuals and interactions over processes and tools" "Responding to change over following a plan" These are 2 of the 4 tenets in the manifesto for agile development [0]. They go on by saying: "That is, while there is value in the items on the right, we value the items on the left more." Essentially, choose tools. Follow processes. Periodically and permanently reevaluate. If following the plan creates an impediment to interactions, or makes the people dissatisfied, respond to these changes. Rinse and repeat. [0] https://agilemanifesto.org/ https://agilemanifesto.org/

andrewflnr 4y ago

That sounds good, sort of a mindset of flexing and changing direction as you move forward. You might call it... agility.

pempem 4y ago

This is the agile suggestion. A previous commenter had it right imho. Its not that the approach isn't working, its that it has been co-opted by management and requires separation to actually succeed. Another note would be that agile itself says: - non team members shouldn't be at stand ups etc. - points shouldn't be used for evaluation of performance (good luck with that) - if management joins anything other than the demo, they should not speak during the meeting (I've had some success here but also always been labeled a curiosity when I push management to be silent)