38

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


21

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


16

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


13

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


9

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


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

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

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

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

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

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.


5

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

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

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


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

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

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


3

I don't think there is a universally well defined difference, but usually "methodology" is used to mean something bigger, more complex and/or more detailed than "method". In my experience, Agile folks don't like the term "methodology" much as it has been traditionally associated with complicated, top-down organized, fundamentally un-agile processes like ...


3

Interesting question, I have given it some though now. I think you make one wrong assumption, and that is why you are confused. First, a very simple and practical, but not fully correct, answer: some sites suggest that model in this would be the same as method (so the first option; e.g. http://istqbexamcertification.com/what-are-the-software-development-...


3

The Project Management Perspective This will vary by organization, and a lot depends on what you're trying to communicate. Formally, the PMBOK calls this stage the "Project Closeout Group" and says that it contains types of closures such as: Project Complete Project Terminated Premature Closure From a more practical project management perspective, this ...


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

Program consist of projects that are somehow related or orchestrated to a common target. For example, in my company we have a customized SAP solution. We implement this solution to every country and cover that country' processes within this customized solution. Each roll-out project including tasks and developments for that roll-out is called a project. And ...


2

Study of different approaches like design, development, operation, and maintenance of software and applicaiton of these concepts can be termed as software engineering. A project involving Software which has fixed goal and limited resources to complete can be termed as software project. I tend to think that to execute a software project you need to ...


2

Formal Definition Wikipedia defines a resource as follows: A resource is a source or supply from which benefit is produced. Typically resources are materials, money, services, staff, or other assets that are transformed to produce benefit and in the process may be consumed or made unavailable. Why People are "Resources" People are the source of ...


2

To echo CodeGnome a little, I would also say that naming sprints is a bad idea. They are ephemeral. Once a sprint has completed you may wish to gather the completed stories into a record for later use in completing user documentation, but aside from that there is nothing to be gained from remembering any particular sprint, and naming them would give them too ...


2

Goals: High level statement referring the possible businesses and allied benefits consequent upon the completion of a project. Objectives: Comparatively low level statement and referring to tangible benefits,consequent upon the completion of a project. Scope: The method to achieve the goals/objectives. Deliverable: The term used in Lump Sum projects, ...


2

This is a trade-off question. It makes perfect sense to prepare for a project. Take a simple project such as upgrading your kitchen. Even if you haven't chosen what the new kitchen will look like, which may include semi major plumbing changes to move the sink from one wall to another, and so on. You may choose to prep that area by trashing or selling ...


2

My definition is far simpler. A project has a defined start, defined scope, and defined finish. A program has an indefinite time and indefinite quantity. It differs from an operations in that operations are intended to be an ongoing concern in perpetuity while a program is intended to end but not known when or to what degree value and quantity are ...


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