Hacker News new | comments | ask | show | jobs | submit login

I have been through waterfall, agile, scrum, "agile", "scrum", kanban, to-do lists. Yet, I cannot point to a single style of project management as a silver bullet. However, I have come to realize the following conditions improve the probability of success: small teams made up of scary-smart accountable people, given a well-articulated objective (not solution) and are left alone without distraction. Short of this, you almost always fall in the trap of micro-management.



> given a well-articulated objective (not solution)

And a clear idea of why the objective is important, or the access to inquire about that. Without the ability to know why a business goal needs to be accomplished, its too easy to start sliding back into asking for solutions rather than objectives.


This is cool and fits well with the mindset that management is not only not part of software development, but it is an inferior category of work. But it is ultimately a useless answer. I am pretty sure the USA basketball Dream Team didn't need any management process too to win the Olympics. How does this help any other team ever?

I am myself for sure not a "scary-smart" person, so it means that I basically will never be on a successful team?

I prefer the answers to this question that apply to mortal developers.


I think you're reading into the answer a little too much. The role of a scrum master is really to shepherd the work through, not micro manage.

In software, a manager's job is to help plan work and shield the team. It is critical that they can do this diplomatically with their peers. Planning involves career guidance, budgets, meetings. If you don't have someone doing those functions properly, the dev team is inundated with distractions.

Scary-smart is buzzwordy and really isn't needed for a team doing CRUD apps of some kind. You need self-sufficient competent people not some "rock star" or "scary smart" person. There's a reason why stereo-types are there indicating those types are hard to work with.


> given a well-articulated objective (not solution)

100% this.

Developer empowerment.

Always has been. Always will be.




Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: