Project management without meetings.
Meeting driven process is a roadblock to delivering better software.
Uclusion is a new way to communicate and track stories at the same time.
"Tools are not discipline" - true but using better communication / process tools does help with discipline. Think of it this way - if you are in charge of tightening screws and you only have a hammer, well the result will not be disciplined for sure.
Software consultant. Bestselling Author. Loves rum, alt culture, games & metal.
Formerly Head of engineering, chief technical architect, head principal engineer, lead dev, etc.
Location
London, UK
Work
Independent Software Consultant at Electric Head Software
I've always favoured what I call "rituals" things people do instinctively because they work for them. Tools can help correctionally, but unless people understand why they're doing the things, they'll never engage with them meaningfully.
You can see this every time someone writes a As a / I can / So that styled user story, and is then unwilling to change it because they don't realise it was meant to be a prompt for a discussion, or every time someone does a stand up and rambles about implementation detail.
Tooling often promotes the artifact, over the process and communication style that is meant to produce it.
Project management without meetings.
Meeting driven process is a roadblock to delivering better software.
Uclusion is a new way to communicate and track stories at the same time.
I agree with you except for the implication that we can somehow remove all tools. Email, chat, group chat, and bug trackers are all tools. Even if we exactly
"The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation."
then that's a meeting and a meeting is a tool. Its not a question of tools versus no tools but of effective tools versus less effective tools. Not understanding the tool set being used comes from not viewing them as tools at all but as some sort of gospel to be followed. If developers correctly understood their communication / process tools then they would question them like they do their IDEA or choice of Javascript framework.
Software consultant. Bestselling Author. Loves rum, alt culture, games & metal.
Formerly Head of engineering, chief technical architect, head principal engineer, lead dev, etc.
Location
London, UK
Work
Independent Software Consultant at Electric Head Software
You can totally remove all tools, but I'd not suggest that :)
Tools are meant to make your working processes easier, but if you don't understand that process regardless of the tools, it's a folly.
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.
"Tools are not discipline" - true but using better communication / process tools does help with discipline. Think of it this way - if you are in charge of tightening screws and you only have a hammer, well the result will not be disciplined for sure.
I've always favoured what I call "rituals" things people do instinctively because they work for them. Tools can help correctionally, but unless people understand why they're doing the things, they'll never engage with them meaningfully.
You can see this every time someone writes a As a / I can / So that styled user story, and is then unwilling to change it because they don't realise it was meant to be a prompt for a discussion, or every time someone does a stand up and rambles about implementation detail.
Tooling often promotes the artifact, over the process and communication style that is meant to produce it.
I agree with you except for the implication that we can somehow remove all tools. Email, chat, group chat, and bug trackers are all tools. Even if we exactly
"The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation."
then that's a meeting and a meeting is a tool. Its not a question of tools versus no tools but of effective tools versus less effective tools. Not understanding the tool set being used comes from not viewing them as tools at all but as some sort of gospel to be followed. If developers correctly understood their communication / process tools then they would question them like they do their IDEA or choice of Javascript framework.
You can totally remove all tools, but I'd not suggest that :)
Tools are meant to make your working processes easier, but if you don't understand that process regardless of the tools, it's a folly.