Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
Kanban value system can be organised into three layers – a familiar core that drives change, a middle layer that is about giving direction and alignment, and a protective outer layer of discipline and working agreements. Or from the outside in: discipline, direction, and drive.
PRINCE2 (an acronym for PRojects IN Controlled Environments) is a de facto process-based method for effective project management. Used extensively by the UK Government, PRINCE2 is also widely recognised and used in the private sector, both in the UK and internationally.
Most software projects involve doing something new about which we’re ignorant, which brings uncertainty. Our brains aren’t comfortable with that, so we have to make conscious effort to stop pretending to be certain when we’re not!
At the beginning of a contract for a software development project, everything often goes swimmingly. The client loves you and you get paid on time, every time. Then, after a few issues or delays, the contract can go a little bit off the rails.
So your software development project is just getting started. Or maybe you’re just about to embark on a new release. Or new members just joined the team. What now? The attention and enthusiasm in your project will never be higher than now. This talk shows how to get the most...
This video describes why Agile methodologies have been developed and contrasts them with a traditionnal software development life cycle approach. It also gives and introduction to Scrum, an Agile framework for software project management.
Even though traditional models and assumptions represent thinking that originated in the 1890s with Taylor (fixation on efficiency and utilisation) and Gantt (of Gantt chart fame) they seem remarkably impervious to change. Our problem is that we need to change otherwise we can never achieve true business agility.
This presentation focuses on improvements made over two years of using Kanban and tries to share some ideas for further work with Kanban.