New answers tagged

1

The team as a whole is responsible for requirements and specifications. Backlog Refinement - preparing backlog items so that they are ready to take into future sprints - is a continuous process. Some teams formally allocate a certain amount of time each sprint to backlog refinement or alternatively just do it as a background task. The point of backlog ...


4

There's a lot of grey area, but the direct answer to you question according to the Scrum Guide is no - it is not the Product Owner's responsibility to provide data mappings. https://scrumguides.org/scrum-guide.html#product-owner So... in your situation, the PO has a backlog item that says something like "As a sales exec, I want to see a graph of sales ...


1

If a company needs to deal with these kinds of technical stories a lot, they hire/have technical product owners. If such stories come up from time to time, then the product owners groom the stories with the support of the software developers in the team. So, my answer is; this is entirely in the scope of the product owner role.


2

Trust is agility's foundation. Lack of trust is painted all over the way the question is framed. The Product Owner is indeed responsible for driving the creation of the user stories. The PO, however, is not the sole responsible for that. Specially on Stories that have a considerable amount of technical background, development team should play a critical, ...


0

You could go "fully Agile" using something called A "Design Sprint". the thing is, the whole team won't be able to work on design and development at the same time. The User Centered Design Process always needs an ahead-approach to the technical team. Also the UX process must consider the technical expertise of the team, the technologies ...


3

TL;DR OKRs are linked to Agile only in so much that the companies that pioneered and promoted the OKR model also adopted significant portions of the Agile Manifesto and the frameworks we consider Agile. However, OKRs are not linked to Agile in any meaningful way. Which means, they can work fantastically well in an Agile environment or go spectacularly wrong....


0

I believe that objectives can work well with agile development if they are aligned with agile values. For example: Responding to change over following a plan - objective is to reduce lead time Working software over comprehensive documentation - frequency of value releases Individuals and interactions over process and tools - demonstrating collaboration, ...


1

Great question! I have read Doerr's book only partially so far - and a couple of other articles. From that, what I have understood is that Key Results cannot be tasks or projects themselves. Even if there's a one-to-one correspondence between a Key Result and what must be done (the task or tasks) to achieve that result, they are separate and distinct. So,...


8

I have delivered several keynote workshops and talks about project management on SpaceX - everything you seek can be found in a careful reading of the book Elon Musk: How the Billionaire CEO of SpaceX and Tesla is Shaping our Future. It is hard to separate the success of SpaceX and Tesla for reasons that become apparent with research, most notably, their co-...


3

Most non-trivial software development work tends to be billed as T&M. The agile approach with a T&M contract is attractive to both the customer and the vendor and generally has important advantages over payment on deliverables: Reduced risk. If a tested, working product is delivered continuously / incrementally then the amount of the work that is &...


1

Meh ... Just go right ahead and define your "story," this being "your encapsulation of a hypothetical user's interaction with your proposed system." Absolutely define it – capture it – any way that seems best. After all, "this is a user story," and a user cannot be expected to know – or to particularly care – how a system ...


2

A good description of the Spotify Model is available on the Spotify Engineering Blog (part 1, part 2). The description of Chapters and Guilds begins in Part 1 at around the 7:30 mark and ends around the 9 minute mark. Like a Community of Practice, Chapters are aligned with competencies. However, the Chapter lead is also the person's line manager. A person is ...


1

It seems that what you have been talking about two years ago, is something many companies are trying to achieve today. Using Waterfall for planning and Agile for execution is now known as a Hybrid project management approach. In such cases, Waterfall practices are used for high-level project management, planning, and setting the course. While Agile comes to ...


Top 50 recent answers are included