Agile Development: Project-Based
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi all,
I have the following doubts:
- I studied months ago that Agile 2.0 (I read it will be deprecated) is split into "Product-Based" and "Project-Based": this division is still valid? If I got well, in the first case Agile is used to manage developments related to implementation stand alone e.g. a new CR that is not connected to a project (so there's no Gantt, tasks...);
also, I got that in the second scenario you could create a Agile phase from the Gantt, in addition to waterfall tasks -> is my comprehension correct?
- Now I found that Agile 2.0 is split into "Standalone project development" (1) and "Project Based" (2) (so the previous classification is deprecated?):
1. I understood that it corresponds to the Hybrid type of project, meaning that in the Gantt you can use tasks (e.g. phases such as planning, and analysis are taken up as waterfall tasks) but you can create an Agile phase to manage the developments (and then the execution is done as agile phase). I read in the product documentation that "Project managers can choose pure agile", how it works in this scenario?
2. I read "Product owners select the prioritized stories and assign them to one or more projects, thus creating the project backlog. Product owners can create one or more projects and capture additional details such as required resources, cost, risk, strategic alignment. .." : but if you create a project from stories, what changed against option 1? If a project is created, then I imagine also tasks are created in a Gantt and so on, then what is different?
- There's a use case when Agile is used regardless of projects?
Many thanks
