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.

New answers tagged

1

Disclaimer: I've never actually used MS Project. Consider, however, exactly what 'resource' means. I have argued before and will argue now that a resource is not an individual and an individual is not a resource. An individual's time is a resource. That being said, why not just create resources for teams' times instead of individuals' times? That way, ...


2

As a new PM/PO I need to do Sprint Planning. As I understand, Sprint Planning is also known as Sprint 0 as nothing is delivered for customers or for internal teams to test/look into. This is not correct. Sprint Planning is a regularly occurring event. It happens once per Sprint and involves the entire Scrum Team. The purpose is to review the Product ...


0

Don't wait for the deadline of the task to receive customers’ feedback If you have stories that cannot be finished because of missing information from your customer, this means that you are not exactly agile. How agile works: The development process has some milestones, in which micro-releases of product are made and feedback from your customer is received....


0

Your understanding is correct. But sprint planning does not take 4-8 weeks. One sprint is created for 1, 2, 4.. weeks, before stating each sprint you need couple of days in order to plan your sprint. When you are planning, for example, 2nd sprint your development team works on 1st sprint. It means you should prepare everything beforehand. In my case scrum ...


0

One of the core elements of Scrum is: Incremental deliveries of "Done" product ensure a potentially useful version of working product is always available. If a story is awaiting answers from your customer at the end of a sprint then it is not "done". This will then be reflected in the number of story points that get completed in the sprint and so will ...


0

This question appears to be based on a false premise. It requires that you accept unclear work into a Sprint. I'd argue that if you have insufficient detail to get work to a done state and receive feedback from your users or clients, you shouldn't start the work. In some cases, if you can't get full clarity from your users before starting work, it may be ...


2

If you read the Agile Manifesto and its principles, you will see wording like: Individuals and interactions ...; Customer collaboration ...; Business people and developers must work together daily throughout the project; The most efficient and effective method of conveying information to and within a development team is face-to-face ...


0

A short answer I have found easy to implement in many different kinds of teams: Create a user story for the discovery session, and treat it like you do any other story. That is, rank it high enough in your Product Backlog to get into the sprint; estimate and task it out (if you do those things); add the developers who choose to be involved; and if that ...


5

Product Backlog Refinement The PO comes with more opportunities for automation. These opportunities need to be reviewed, sized and an effort estimation need to be provided, i.e. a discovery session is needed. What you're calling a "discovery session" is actually a defined event in Scrum called Product Backlog refinement. [Refinement] is an ongoing ...


5

The development team is already busy working in the current sprint One of the principles in the Scrum Guide is that a Scrum team spends time during the sprint refining their backlog of work. This can represent up to 10% of the time in the sprint. In your situation this backlog refinement would include discovery sessions, review, etc. How the refinement is ...


Top 50 recent answers are included