Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects
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.
“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.
This article describes a recent experience with a software development project trying to adopt the Agile methodology without enough guidance. This methodology is then compared with the traditional Waterfall approach, the potential advantages and pitfalls of both being compared. It is assumed that readers have basic understanding of both methodologies.