Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
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

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


3

If Activity B cannot begin before Activity A is complete, it's a finish-start dependency, in PM-speak. Alternatively, if both activities have to start at the same time (pretty rare), it's a start-start dependency. If both activities have to end at the same time, it's a finish-finish dependency.


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

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

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 ...


2

Some things to think about based on what I've observed from your question: While defining stories we had two stories one larger one that would allow some infrastructure to be made and a smaller ticket that had more apparent value that depended on it. Together they were bigger than we were happy with a story being. This stuck out to me because it ...


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. It ...


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 ...


1

I assume this dependency in jira is with a link between the issues such as "is blocked by" A possible Solution in jira would be: Your board is fed by a filter. You can edit this filter to exclude issues blocked by items in the sprint (you may need to use advance jql functions like the ones scriprunner provides). If these issues are not in your backlog, ...


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