36

Each organization and author has a different definition for these terms. In this article, Mike Cohn provides his definition of User Stories, Epics and Themes: A user story is simply something a user wants. User stories are more than just text written on an index card but for our purposes here, just think of user story as a bit of text saying ...


27

While they seem similar, there are distinct differences. Product Management has to do with the 'product' itself - design, features, audience, pricing, marketing, profitability, etc. Project Management focuses on delivering the product. Example - The intended market needs to be researched - the act of researching (who to research, how to conduct, what ...


26

Other than Projects tending to be short-term and Products tending to be ongoing endeavours, is there a difference in the two? The key difference is fairly simple: Product management: is responsible for discovery and definition of the scope. Project management: is responsible for execution and delivery of the scope.


16

TL;DR I was wondering if it's a good idea to name Sprints with user-friendly names instead of using numerals like Sprint 1, Sprint 2, etc. No, it's not a good idea. A sprint is a container where Product Backlog items are temporarily stored for a brief duration. A sprint may produce some project artifacts, but the sprint itself has value only as a time-...


15

Name the Sprint after the Sprint Goal If you want to name a Sprint, I agree with the accepted answer in the programmers.stackexchange.com thread that you should name it after the Sprint Goal. As the Scrum Master, I keep pushing the Product Owners to come up with a well articulated Sprint Goal. I always start my Sprint Planning sessions by inviting the ...


12

There are different conventions I've seen used. In my opinion, even having one is completely irrelevant, besides giving you something to refer to in discussions (which may or may not be a good thing!) Use a «Sprint N» or «Iteration N» convention: Pro: Easily generated Con: Is anyone going to remember what you did in iteration 23? It's almost like not naming ...


11

I would refer to these as "Iterations." You can describe your process in terms of iterations to your clients -- e.g. We work in two week iterations. That means, on day one, we identify the work we're going to do in the next two weeks.... etc...


10

Projects don't have to be short-term; they can be long-term. The only requirement for a project is: it must produce something, and it must have an end. If it takes 2 years or 2 weeks to finish it can still be a project, and fall under the domain of the project manager. I tend to think of product managers as being a special case of the project manager, a ...


9

My mneumonic is that Quality Assurance is a Process (spot the double 's' in each). Quality control is testing. If you search on QA vs QC you'll get a number of sites; I happen to find these rather clear: Quality assurance is about engineering “processes“that assure quality. Now let’s try to understand it better! Infostretch Quality Assurance is ...


9

I thought it is a some kind of a slang, but now I've also spent some time searching, and I think it comes from the tool they are using (the OP mentioned agilo for trac). According to a discussion on the tool's google group the battery is a feature which can be used to add contingents to a sprint: A Contingent is an amount of time subtracted from the Team ...


9

Cone of Uncertainty Research in the software industry on the Cone of Uncertainty stated that in the beginning of the project life cycle (i.e. before gathering of requirements) estimates have in general an uncertainty of factor 4 on both the high side and the low side (Boehm 1981). This means that the actual effort or scope can be 4 times or 1/4 of the first ...


7

Goal and Objective are very similar. As a rule, goals are a bit broader and describe the direction you're attempting to move in, while objectives are more specific and are often measurable. That said, definitions may vary and I would try to agree on a definition in your team, department, or company so that everyone is on the same page. Scope is the body of ...


7

The concept of an Epic is related to that of User Stories, which come from Extreme Programming. There are two primary definitions for what an Epic is. In some cases, it refers to a very large User Story that needs to be broken down and decomposed into smaller User Stories that represent value-adding work that can be delivered. In other cases, it can be used ...


6

Project managers walk away from a project after a period of time. Product managers are there for life (the life cycle of the product). Project managers are akin to the midwife - they stay around long enough to bring the product to market. Product managers are akin to mothers - we define, launch and then nurture the product through all it's stages. See ...


6

I would like to start from their name. Quality assurance - it's a support of an application/project, which assumes that every quality requirements will be checked at the end of the project. The assurance may include the whole procedure, the logistic of the testing and fixing every bug and problem. It can be also preventing a problem and implementing quality ...


6

It sounds like the Cone of Uncertainty. The idea is that at the beginning of a project or effort, there is enough uncertainty that estimates are generally in the range of being 4x over or 1/4 of the time it will take to complete. As the project progresses, these uncertainties begin to be resolved or better understood and the range of estimation becomes ...


5

Managing your resources--making tough decisions on how to deploy your financial, tools, materials, and humans--to minimize the threat of failure and maximize the likelihood of success AND treating people kindly, humanly, and with respect are two different things. It is YOUR definition that makes a resource a thing. Dictionary.com defines it as: a source of ...


5

Just to add more words to help clarify: QA is proactive--creating the capability to reduce the defects in development. QC is retroactive--finding the defects already created to fix. Think of QA as risk mitigation while QC is risk contingency. I differ in meszar's answer only in that QC is NOT part of QA, in my view. Two different capabilities, ...


5

There is, of course, difference between method and methodology terms, since etymologically methodology is theory of methods. Saying it simply and not being entirely accurate, a method is a way of doing things, and a methodology is a collection of methods. Dictionary definitions describe briefly these terms: methodology: A set of methods, rules, or ideas ...


5

Ongoing work of fixed type is generally called "Operations". Hence why in traditional PMI a project has a hand off to operations. When an amusement park is built, it's a project. When it is done, it is handed over to an operations team to run it.


4

Public Sector Terms Every industry and sector has its own patois. In the public sector, agile practices are generally referred to as "modular development," and sprints deliver "increments" or "useful segments." See page 7 of Contracting Guidance to Support Modular Development for an example. Private Sector Terms For companies that understand agile ...


4

Traditionally in the UK, task and finish is the term for a way of being paid. By completed task, not by hour or by "piece"(unit produced). For example a refuse (garbage) collection team are contracted to work 5 days a week, 7.5 hours/day. Each day's collection route (100 streets or whatever) is known to represent 7.5 hours work on average. But if today they ...


4

I have a slightly different take on this. Our team has evolved an approach (branching model, organisational structure, overall approach) which allows us to run multiple sprints in parallel - this is especially useful for ensuring high utilisation, so nobody is sat idle waiting for QA to finish their task. The downside is, at any given point, we don't know ...


4

As far as I know the title of this role is "PMO Manager".


4

This is based on personal experience, so if it differs from your own, feel free to jump in. Development - refers to the primary implementation of new projects. Once an initial development project is complete, and the clients/stakeholders have accepted it, then you will typically move into a new phase--either maintenance or enhancement. Maintenance - refers ...


4

The key is here.... ...to obtain benefits not available from managing them individually A Project is the smallest element that has self-contained benefit. A Programme aggregates those benefits into a strategy. Building a hotel is a project. It has a benefit. You can create 'sub-projects' out of each floor but their benefit is not realised until the hotel ...


3

They can be the same and often times product managers are forced to take on the role of Project Managers, but I see the functions as fundamentally different. In relationship to projects: Many times your Product Manager will be a project sponsor. They decide the change. They decide what to do, what the requirements are, what the business drivers are, and ...


3

I would agree with Lunivore and SBWorks - their inputs are from both an academic and from a professional industry-based perspective - seasoned with common sense and an understanding of the English langauge (which is pretty LOW in the UK, Australia, Canada, NZ and the USA - I constantly see immigrants who have a good laugh at the local's language disasters) ...


3

Not sure how it came to be, but in my last two companies we used the following Sprint naming format: Year+StartWeekNumber+Teamname. Resulting in something like "2016W10 Team Blue" for our current sprint. But in the last 7 years of doing Scrum I never felt the need to use the Sprint numbers after the sprint was done. Although sometimes it might be handy to ...


3

In the environments I have worked in, new development is green field work where there no existing system in the target software platform. This may be a reimplementation of an existing system, or development of a new system. The scope of new development is usually quite large. Examples: Writing a time and billing system to replace an existing platform. ...


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