Most recent blogs in the Management category
It’s common for NFRs to take a back seat in requirement gathering sessions. Topics like scalability and security are rarely met with the same excitement or urgency as customer facing features, yet they are critical to a development project’s success.
The goal of this initial preparatory Sprint is to front-load any work necessary to allow the teams to commence Sprint 1 effectively and without impediments. This includes preparing the Project Roadmap, creating the basic skeleton and plumbing for the project and readying the team for feature development.
This week I had cause to remind a couple of colleagues of the 'iron triangle' - a representation of the relationship between the forces that combine to constrain any project. Sometimes also referred to as the 'scope triangle' or 'quality triangle', it is also a traditional measure of project success.
No, this is not another meaningless political slogan. I just want to tell a quick story about some fantastic work we've completed for one of our major clients. Something a bit out of the ordinary from what we normally boast about, and something our team is quite proud of. It also reminded me why we are in this game, the IT industry: to support the business.
A collection of basic mistakes that you should never make when using JIRA. So if you want to put "Working knowledge of JIRA" on your CV, make sure you are not committing any of these sins.
Nobody can be expected to recall the events that occurred in a meeting six months prior to release of a project. We document so that everybody understands the scope of work in such sufficient detail as to produce outstanding work.
Bootstrap has been around for a few years now, and everything I'd read about it told me what a fantastic front-end framework it is. That everything is faster and easier and it can save web developers heaps of time. Unfortunately, that's also about all I knew about Bootstrap. Ignorance is bliss, right?
As the project manager, it's no fun having a fully designed and developed website - i.e. technically and functionally ready for launch - when it's still full of gaping holes where content is supposed to be.
Daily stand up meetings energize and empower teams to create better software.
Retrospective sessions help us learn from our experiences and improve the way we work both independently and as a team. Getting together and discussing “how things went” is one approach but for the session to be truly valuable we need to add a little structure to the conversation.
Building a killer product? Learn how to apply proven psychological techniques to grow your user base.
Microsoft products can be useful, and their enormous market share means that everyone knows how to use them. But are they always the best tools for the job?
A brief look at old and new school approaches to team culture and the astounding benefits that many companies are afraid to explore.
It looks like I'm out of a job. And it turns out that everybody who thinks they're doing agile right, is not. Who the bloody hell created this agile lunacy? And if it's so bloody hard to get right, then why is it apparently the ducks nuts of software development? Derp derp.
There is no right or wrong way to manage clients, web designers and design feedback. Groundwork, baby-steps, helping each other and remaining friends is a pretty good start though.