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

See: Agile

From [ https://en.wikipedia.org/wiki/User:Guy_Macon/Wikipedia_has_C... ]:

"In particular, their poor handling of software development has been well known for many years. The answer to the WMF's problems with software development has been well known for decades and is extensively documented in books such as The Mythical Man-Month and Peopleware: Productive Projects and Teams, yet I have never seen any evidence that the WMF has been following standard software engineering principles that were well-known when Mythical Man-Month was first published in 1975. If they had, we would be seeing things like requirements documents and schedules with measurable milestones. This failure is almost certainly a systemic problem directly caused by top management, not by the developers doing the actual work."

"This is not to imply that decades-old software development methods are somehow superior to modern ones, but rather that the WMF is violating basic principles that are common to both. Nothing about Agile or SCRUM means that the developers do not have to talk to end users, create requirements, or meet milestones. In fact, modern software development methods require more communication and interaction with the final end users. Take as an example the way Visual Editor was developed. There are many pages of documentation on the WMF servers and mailing lists, but no evidence that any developer had any serious discussions with the actual editors of Wikipedia who would be using the software. Instead. the role of "customer" was played by paid WMF staffers who thought that they knew what Wikipedia editors need better than the editors themselves do. Then they threw the result over the wall, and the community of Wikipedia editors largely rejected it. Or Knowledge Engine, which was developed in secret before being cancelled when word got out about what the WMF was planning. Another example: The MediaWiki edit toolbar ended up being used by a whopping 0.03% of active editors."

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