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.
Ever wondered why your software development team just don’t seem to have fun at work, why everyone always seems to be late for meetings by at least one minute.Most people believe motivation comes from paying people more money, is this the only way?
Have you ever worked in a software development super team? The kind of team where the process is the natural flow of the team. Everyone on the team working on his or her parts of the project and it all comes together as one perfect whole. Discussions flow easily, decisions...
If you’re worrying about how you’re doing, you’re not paying attention to what you’re doing. When you’re panicking, you’re not improving. This lightning talk explores the value of focusing on process rather than progress in order to deliver quality while staying sane.
In real world agile teams, traditionally defined rigid roles are rapidly being displaced by a culture of collective ownership of the product. Responsibilities are being decoupled from specialties by a collection of operators with overlapping skills, and chief among them is technical acumen.
Estimates are required multiple times in a project. Project members need to make estimates for a variety of reasons: the amount of time for a task; the cost for resources; the cost of software, hardware and other materials; the time required to finish a task.