Nice post!
Have this experience that since most companies has some timeconsuming sort of Agile way of working with sprints, sprint planning, backlog grooming, Scrum poker, Scrum masters etc. etc. this also means they do not have the time or manpower to apply other methodologies or routines relevant for the company itself or industryrelated ones.
Such as documenting requirements ..
The story is always the same "..just pick a User story or task from the todo column in the board.."
Well, problem is that the task at hand is described with a few words in the header of the card ;)
I was an architect once having responsibilities for 8 developers, I spent half my day in meetings; Grooming sessions, velocity evaluation sessions, 2 standups each day, each lasting for 45 minutes, etc, etc, etc ...
According to neutral research in the subject the average software developer is supposed to be able to create between 325 and 750 lines of code per month. Ignoring whether or not this is a good metric for productivity, my devs (8 devs) delivered 23 lines of code in two months.
When I asked for help from my manager, his reply was; "Stop being so darn productive" - I delivered my resignation a week later ... :/
That's agile used for managers control, which Is, I believe how most companies apply it, and Is pretty much against agile principles.
I dont think ther Is anything inherently bad about those methodologies. You should use whatever suits the culture of the company, the nature of your product, buisness and the need of your users or clients
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice post!
Have this experience that since most companies has some timeconsuming sort of Agile way of working with sprints, sprint planning, backlog grooming, Scrum poker, Scrum masters etc. etc. this also means they do not have the time or manpower to apply other methodologies or routines relevant for the company itself or industryrelated ones.
Such as documenting requirements ..
The story is always the same "..just pick a User story or task from the todo column in the board.."
Well, problem is that the task at hand is described with a few words in the header of the card ;)
I was an architect once having responsibilities for 8 developers, I spent half my day in meetings; Grooming sessions, velocity evaluation sessions, 2 standups each day, each lasting for 45 minutes, etc, etc, etc ...
According to neutral research in the subject the average software developer is supposed to be able to create between 325 and 750 lines of code per month. Ignoring whether or not this is a good metric for productivity, my devs (8 devs) delivered 23 lines of code in two months.
When I asked for help from my manager, his reply was; "Stop being so darn productive" - I delivered my resignation a week later ... :/
That's agile used for managers control, which Is, I believe how most companies apply it, and Is pretty much against agile principles.
I dont think ther Is anything inherently bad about those methodologies. You should use whatever suits the culture of the company, the nature of your product, buisness and the need of your users or clients