5

A lot can be done using mocks and stubs. For example, the team could work out what the API will look like first and then rapidly build a stub API that returns fake data. This helps to separate out the frontend and back-end development tasks. Now the frontend developers work using the stub and the back-end developers work to flesh out the implementation of ...


3

For estimation, you want to estimate at the Product Backlog Item level. If you're using User Stories, the User Story is typically the Product Backlog Item. And when estimating, you want to account for all of the work necessary to get it to its done state, per the team's Definition of Done any any acceptance criteria on the Story itself. The best way to ...


3

I would say "blocked" for the first one and one of "unblocked", "ready" or "to do" for the second one.


3

Might be too broad to be answered, but I'll give it a crack. First, by In the meantime a former decision maker is still with one foot in and I am in charge of decision making now I assume you mean that there's a highly-placed employee that is still interested in the project, but no longer has authority. So, first thing is to touch base with him to ...


3

Optimize Terminology for Clarity of Communications You are describing phase gates. There isn’t a universally-accepted set of terms for your desired project states, but each phase should have a set of project-specific status labels that communicate the state of the project or the gating criteria. An organizational or project glossary is typically where you ...


2

You need to get VISIBILITY into what's happening there. Right now you seem to be mostly blind to what's going on and you are forced to trust this external provider. A 3 months estimate turned into a 9 month one. Any chance for the 9 month estimate to later turn into 12 months? Check your contract and see what the agreed deliverables are. Do they deliver ...


2

When doing estimate, should each part be estimated separately? How to calculate "total" estimate? All the teams participate in the same Sprint Planning, discuss all the aspect of the User Story and fully estimate it. How? You first need a reference User Story which has 1 Story Point. You discuss this User Story so that all the parts are understood....


2

This is probably a better fit for English Language & Usage than pmse. From a project management standpoint, it doesn't really matter as long as you pick a term and stick with it. For the first: "Is blocked, is blocked by '---', is dependent on '---', etc." For the second: "Was blocked, was blocked by '---', was dependent on '---', is unblocked, is ...


1

As others have indicated, your contract should detail how to resolve a dispute with your vendor and you're on the hook to follow those terms. My first action would be to work with the vendor so I can attempt to understand the true health of their work; I would provide them with a deadline of a few days to bring forth verifiable evidence of what is completed ...


1

Nine months or even three months without any delivery is already a red flag. De-scoping in order to meet a deadline that is still months away also seems like a poor way to manage a project. However, extracting the project from the agency, attractive though that may seem, would surely incur some significant risks and costs. Firstly, understand what is their ...


1

RAID logs are not usually maintained when working with Scrum. The reasons for this include: We release frequently, which often reduces risk Frequent releases also reduce the need for assumptions Agile favours individuals and interactions over process and so we prefer to regularly discuss things rather than to rely on documentation The Scrum retrospective is ...


Only top voted, non community-wiki answers of a minimum length are eligible