Creating a New Project in Archy for Jira
Objective
To provide a clear and structured process for team members to create a new project in Archy, ensuring that all necessary steps are followed to minimize misunderstandings and errors while maximizing productivity and accuracy.
Key Steps
- Initiate a New Project in Archy
- Open the Archy plugin within Jira.
- Select the option to create a new project.
- Define Project Details
- Enter a predefined project name (e.g., “Merchant Financial Aggregation Platform”).
- Confirm that the project type is set to “Scrum-based.”
- Establish Project Hierarchy
- Set up the project hierarchy by defining the epics and user stories.
- Upload Business Requirements Document
- Copy and paste the contents of the Business Requirements Document into Archy. This document should outline the key functionalities and use cases for the project.
- Generate Initial Product Backlog Items (PBIs)
- Use Archy to generate the initial set of epics and user stories based on the Business Requirements Document.
- Review the generated items for relevance and accuracy.
- Refine Epics and User Stories
- Edit the descriptions of epics and user stories as necessary to ensure they align with project goals.
- Use the regenerate feature in Archy to suggest additional epics or user stories based on the current project requirements.
- Batch Refine User Stories
- If needed, select multiple user stories and refine them in batches for efficiency.
- Final Review and Adjustments
- Ensure all epics and user stories are complete and accurately reflect the project scope.
- Use Archy to suggest additional user stories if there are gaps in the backlog.
- Save the Backlog to Jira
- Once satisfied with the backlog, save it to Jira to kick off the development process.
- Start Implementation
- Access the saved backlog in Jira to begin the implementation phase of the project.
Cautionary Notes
- Ensure that the Business Requirements Document is comprehensive and clear before starting the project setup.
- Be cautious when using the regenerate feature, as it may remove existing user stories that have not been backed up.
- Regularly save your progress to avoid losing any data or changes made during the setup process.
Tips for Efficiency
- Use templates for the Business Requirements Document to speed up the initial setup.
- Familiarize yourself with Archy’s features to maximize the use of its capabilities in generating and refining backlog items.
- Consider scheduling regular check-ins with team members to review the backlog and make necessary adjustments collaboratively.
- Utilize the like and dislike buttons in Archy to help improve its suggestions over time.
By following these steps, team members will be able to create a new project in Archy efficiently and effectively, leading to a well-structured backlog and a successful project kickoff.
Streamlining Project Management with Archy in Jira
1. Introduction
- Purpose of the demo: To showcase how to start a new project using Archy, a plugin for Jira.
- Overview of the project: Development of a merchant financial aggregation platform.
2. Project Setup
- Creating a new scrum-based project in Jira.
- Pre-defined project name: Merchant financial aggregation platform.
- Description of the platform’s purpose: Aggregating financial activities for merchants.
3. Initial Project Requirements
- Introduction to the Business Requirements Document (BRD).
- Key topics included in the BRD:
- Invoicing and quotes management.
- Business to business payments.
- Investment management.
4. Generating the Product Backlog
- Using Archy to generate initial epics and user stories based on the BRD.
- Overview of the hierarchy: Epics and user stories.
- Explanation of the initial set of epics and user stories generated by Archy.
5. Refining the Backlog
- Options for refining the backlog:
- Regenerating new epics and user stories.
- Editing existing epics and user stories.
- Steps to refine epic descriptions for more detail.
- Generating additional user stories based on epic descriptions.
6. Enhancing User Stories
- Importance of refining user stories for clarity and detail.
- Options for batch refining user stories.
- Generating more user stories based on existing epic descriptions.
7. Finalizing the Backlog
- Manual addition and editing of user stories.
- Utilizing like and dislike buttons for Archy’s learning process.
- Saving the finalized backlog to Jira for implementation.
8. Conclusion
- Overview of the completed backlog with epics and user stories.
- Readiness to kick off the development process using the structured backlog created with Archy.
Streamlining Project Management with Archy in Jira
1. Introduction
- Purpose of the demo: To showcase how to start a new project using Archy, a plugin for Jira.
- Overview of the project: Development of a merchant financial aggregation platform.
2. Project Setup
- Creating a new scrum-based project in Jira.
- Pre-defined project name: Merchant financial aggregation platform.
- Description of the platform’s purpose: Aggregating financial activities for merchants.
3. Initial Project Requirements
- Introduction to the Business Requirements Document (BRD).
- Key topics included in the BRD:
- Invoicing and quotes management.
- Business to business payments.
- Investment management.
4. Generating the Product Backlog
- Using Archy to generate initial epics and user stories based on the BRD.
- Overview of the hierarchy: Epics and user stories.
- Explanation of the initial set of epics and user stories generated by Archy.
5. Refining the Backlog
- Options for refining the backlog:
- Regenerating new epics and user stories.
- Editing existing epics and user stories.
- Steps to refine epic descriptions for more detail.
- Generating additional user stories based on epic descriptions.
6. Enhancing User Stories
- Importance of refining user stories for clarity and detail.
- Options for batch refining user stories.
- Generating more user stories based on existing epic descriptions.
7. Finalizing the Backlog
- Manual addition and editing of user stories.
- Utilizing like and dislike buttons for Archy’s learning process.
- Saving the finalized backlog to Jira for implementation.
8. Conclusion
- Overview of the completed backlog with epics and user stories.
- Readiness to kick off the development process using the structured backlog created with Archy.
