Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
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.
“Honesty is the best policy. Truth will out. In vino, veritas.” We have many quotations and sayings which call out honesty and truthfulness to be strong, always winning out over lies and politics. Could it be the same in project management?
This video discusses the four values of Agile: responding to change over following a plan, customer collaboration over contract negotiation, working software over comprehensive documentation, individuals and interactions over process and tools.
Software development is an industry that has been around for a little bit more than 50 years. There are a lot of really smart people working in this industry. How is it possible that these smart people are so good at failing software development projects? How can we as an...
Focussing on empowered professional software engineers, well defined testing strategy, process automation, high investment in people development, requirements management and strong emphasis on quality.
As Agile approaches like Scrum are supposed to be dominant for enterprise software project management, the latest Methods & Tools survey asked the following question: Which project management approach is used by your project? The results make us think that the situation is a little bit more complex than the...
Continuous Delivery is a revolutionary new concept in business agility that can help large enterprises become as lean, agile and innovative as startups — making it possible to continuously adapt software in line with user feedback, shifts in the market and changes to business strategy.
With only a few principles which Kanban prescribes it can’t be treated as a method which directly shows how to organize a team or the way it works. What more, it is advised to start Kanban implementation without changing the process which is currently in place.