MoSCoW prioritisation is a method for collating all your features, user stories and feature requests into an sense of order, identifying what is most important and therefore should be delivered first or given the most concentration, within software development projects.

My particular umbrage with MoSCoW is the “Won’t have”. In my opinion this is wrong, it’s negative, it dismisses features or requirements because there isn’t enough time to complete them all. A perfectly valid viewpoint I hear you say – but in my experience dismissing any feature or requirement at the stage of a project wherein you would use MoSCoW is far too early to begin dismissing anything.

Continue reading

Last year, June 2016 to be exact, I took part in my very first company “HackFu” event. I had decided that my first years’ attendance would be as a competitor, to get a feel for the event from an attendees point of view, before attempting to become part of the team that would organise and run the event for the following year.

“HackFu” is a two day, completely immersive, story based, learning and development event, run by MWR InfoSecurity for its employees – and most recently organised and developed by chronyko, for MWR. In the month before the event attendees begin to receive parts of the storyline, beginning with some soft detail before getting into the hardcore minutia shortly before the event. The entire event is themed, and actors are brought in to portray characters within the storyline.

Continue reading