Controlling Agile Projects
In agile projects, there is a disturbing complacency about failure. We are used to statements like «I’ve seen no software project delivered on time, on budget». Do you really think this a problem without a solution? If we let the team do their tasks but nobody is accountable for the project, why is it a surprise when the project is behind schedule and over budget? Agile projects must be controlled as well.
Agile Case Study (5/5): Closing the First Release
This is the fifth and last post on the chapter 23 of the book Agile Estimating and Planning, by Mike Cohn. In the previous post the team was about to start the first 2 week iteration, planned with 4 stories and 18 points. They also forecasted a…
Agile Case Study (4/5): Release Planning
Fourth post on the chapter 23 of the book Agile Estimating and Planning, by Mike Cohn. In the previous post the Havannah team met with on this agenda: First sprint planning. Market research outcomes review. Initial estimate for the release plan and the project schedule. First point…
Agile Case Study (3/5): Planning the First Sprint
Third post on the chapter 23 of the book Agile Estimating and Planning, by Mike Cohn. In the previous post the Havannah team had written 32 user stories, totaling 146 story points. In this post, team members are working on another project, while analyst Delanie start a…
Agile Case Study (2/5): User Stories
Let’s continue reading chapter 23 of the book Agile Estimating and Planning, by Mike Cohn. In this second post you will realize about the convenience of writing down physical cards and how to conduct a brainstorming session to make team members infer requirements, a.k.a. user stories. A piece…
Agile Case Study (1/5): Project kick-off
The following case study is originally published as the chapter 23 of the Mike Cohn’s book entitled Agile Estimating and Planning. In this chapter, the author, in order to summarize and put into practice many key points explained in the book, develops a case on…
Citizen Development in The Project Economy
A citizen developer is a user without coding knowledge who creates new business applications for consumption by others using LCNC Development Platforms sanctioned by corporate IT. By 2024, more than 65% of software projects in the project economy will include at least one citizen developer. This doesn’t mean software teams will ignore IT, rather the opposite.
Closing Projects with PMPeople
While closing a project or phase, PMPeople can help effective communication with stakeholders, specially nervours since they know they won’t have the right to request more changes and they need to make sure all their requirements are met. You can control this communication, any time, anywhere, with PMPeople.
PM² Artefacts with PMPeople
The PM² Guide describes 33 document templates covering most cases in all kind of projects, not just UE’s ones. Many projects need to follow a strict methodology based on documented evidence. Even for those cases, PMPeople enables people to collaborate first, and document the project later, saving time and fostering project teams productivity.
The Dark Side of Agile Projects
Agile frameworks do not mention the role of the project manager because they were designed for product management, not project management. However, the PM role is required when the organization approves a project that must be completed within a certain period of time and below a certain budget. Professional PMs are responsible, among other things, for the agile project to end on time and on budget, meeting stakeholders’ requirements.
- Business (11)
- Demand Management Roles (3)
- Frequently Asked Questions (3)
- Guide (20)
- People (11)
- Process (6)
- Project Management (41)
- Supply Management Roles (1)
- Training (4)
- Uncategorized (1)