Features journey - Revision history

Root: /* Analysis phase */

2025-10-20T20:38:00Z

Analysis phase

← Older revision		Revision as of 21:38, 20 October 2025
Line 56:		Line 56:

	We need to make sure that we can measure the impact of the feature we have developed. Data department has to analyze the impact of the feature in the project.		We need to make sure that we can measure the impact of the feature we have developed. Data department has to analyze the impact of the feature in the project.
	~~<!-- From bodyContent 1542907.mraw -->~~

	[[Category:achieve objectives]]		[[Category:achieve objectives]]

Maintenance script: Added category achieve objectives

2025-10-19T17:51:41Z

Added category achieve objectives

← Older revision		Revision as of 18:51, 19 October 2025
Line 58:		Line 58:
	<!-- From bodyContent 1542907.mraw -->		<!-- From bodyContent 1542907.mraw -->

			[[Category:achieve objectives]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC Project/Project management/achieve objectives/Features journey to Features journey: Cleaned title and categorized

2025-10-19T17:51:41Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC Project/Project management/achieve objectives/Features journey to Features journey: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 16:25, 17 April 2025

2025-04-17T16:25:56Z

← Older revision		Revision as of 17:25, 17 April 2025
Line 1:		Line 1:
			In order to have an Agile flow, we must follow this steps when deciding to develop a new feature:

			<span id="initial-definition"></span>
			= initial definition =

			Create an initial draft with the ideas of what wants to be achieved with this feature. Remember to be [[UserDocumentation:Knowledge_Central/KC_Data_office/Data-driven_culture\|Data driven]] and take [[UserDocumentation:Knowledge_Central/KC_Data_office/Data-driven_decisions\|data-driven decisions]]

			<span id="initial-estimation"></span>
			= Initial estimation =

			Before planning to start the feature once it has an initial definition, make an initial estimation of the time cost to implement that feature with the departments leads. With that initial estimation, Project Manager can determine if it’s reasonable to develop the feature, and when to do it based on the time estimation. Departments that are involved:

			* Design
			* Development
			* QA
			* Data Office

			<span id="add-the-feature-to-the-backlog"></span>
			= Add the feature to the backlog =

			Once the feature has been properly defined and it has an estimation, it can be added to the project backlog to know that it has been proposed to be developed.

			<span id="design-along-with-it"></span>
			= Design along with IT =

			When it has been decided that the feature needs to be implemented, if feature requires design department, there must be a grooming meet with Product, Design and IT in order to define the easiest way to implement the task for each department.

			<span id="check-task-requirements"></span>
			= Check task requirements =

			After all these meetings, we need to be sure that task definition is properly completed and well documented. In order to have a good definition, for tasks that take more than a day, [[UserDocumentation:Platform/Tasks_&_Features\|document them in confluence]], not just in the Jira task. Departments of Product, Design, IT and QA need to agree that all requirements are properly defined.

			<span id="refined-estimations"></span>
			= Refined estimations =

			The next step is to present the feature to the different departments and make a thorough refinement. Each department must go through the feature definition and:

			* check that all requirements are clear. If there are any doubts during this phase, department lead has to communicate with Product responsible to clarify them.

			<span id="development-phase"></span>
			= Development phase =

			Feature development need to be done in these steps:

			* Design
			* Code
			* Test

			<span id="deployment"></span>
			= Deployment =

			Once the feature has been properly tested and accepted by its responsible, it can be moved to production environment

			<span id="analysis-phase"></span>
			= Analysis phase =

			We need to make sure that we can measure the impact of the feature we have developed. Data department has to analyze the impact of the feature in the project.
	<!-- From bodyContent 1542907.mraw -->		<!-- From bodyContent 1542907.mraw -->

imported>Unknown user at 16:25, 17 April 2025

2025-04-17T16:25:56Z

← Older revision	Revision as of 17:25, 17 April 2025
(No difference)

imported>Unknown user at 16:25, 17 April 2025

2025-04-17T16:25:56Z

New page