Apprentice PM - Launch Course
Definition of Ready (DoR)
- User Story is written
- Acceptance criteria is completed
- Bounty 1 is completed
- Articulate the goal of your project in https://discord.com/channels/834499078434979890/1066116689978208296
- Select a tool to organize your work and provide a link in: https://discord.com/channels/834499078434979890/1066116689978208296
- Document the goal in the tool you have selected and then next steps as a subtasks.
- Share with
for Feedback
User Story:
As a member of the Project Management Guild in the Bankless DAO, I want to be able to access a comprehensive course on Web3 Project management skills, so that I can improve my ability to coordinate and manage projects in the decentralized and autonomous Web3 ecosystem.
Acceptance Criteria:
- The course covers the key competencies, skills, and responsibilities that are specific to Web3 PMs covered in the Competency Matrix
- The course includes practical examples and case studies that are relevant to the guild's work in the Web3 ecosystem. (May not be necessary for this course)
- The course is self-paced and accessible online, with clear instructions and navigation for users.
- The course includes quizzes, assessments, and interactive elements that help users to test their understanding and retention of the material.
- The course is reviewed and approved by the Project Management Role Holders in the PM guild before being made available to members.
- Members of the guild have access to the course and are able to provide feedback and ask questions on the content.
- The course has instructions and a defined cadence regularly reviewed and updated to ensure the information is current and relevant.
- The course is hosted on the Bankless Academy platform.
- The course is properly labeled and categorized on the Bankless Academy platform, making it easy for users to find and access.
- The course includes all necessary information, such as a course description, learning objectives, and prerequisites.
- The course is visually appealing and easy to navigate, with a clear structure and organization.
- The course includes relevant graphics and graphic design throughout and on selected pages.
- The course has been reviewed and approved by the Bankless Academy team and meets their quality standards.
- The course is properly integrated with the Academy's analytics and tracking system, allowing the team to monitor usage and engagement.
- A course completion credential is designed, created and approved by the PM Guild.
- The course provides a mint-able credential that follows the implementation pattern already established by Bankless Academy
Bounties
Definitions:
A "definition of ready" (DoR):
Is a set of criteria that must be met before a user story or product backlog item can be considered ready for development. The definition of ready is used to ensure that the development team has a clear understanding of the requirements and constraints of a user story, and that all necessary information and resources are available before development begins.
User Story:
A user story is a tool used in agile software development to capture a description of a software feature from an end-user's perspective. A user story is a simple, brief statement that describes a feature or functionality from the user's point of view. It is typically written in the format of
As a [user], I want [some goal or feature], so that [some reason].
The purpose of a user story is to provide a clear, concise, and user-centered description of the feature or functionality that the development team will be working on. It is a way to express the requirements of the software in a way that is easily understood by both the development team and the stakeholders. User stories are often used in Agile development methodologies such as Scrum and Kanban, as they provide a way to break down large, complex projects into smaller, more manageable chunks of work.
User stories are usually written by a product owner, who represents the interests of the stakeholders, or by the stakeholders themselves. They are designed to be short, simple and easy to understand, so that the development team can quickly understand the feature they are going to build. They also often include acceptance criteria, which are specific conditions that must be met for the story to be considered complete, it also helps to ensure that the final product will meet the needs of the users.
User stories are also a way to ensure that the development team is focused on delivering value to the users, as it helps to ensure that the software being developed is solving the right problems for the right people.
Acceptance Criteria:
Acceptance criteria are a set of specific conditions that must be met in order for a product or deliverable to be considered complete and accepted by the stakeholders. These criteria are used to define the scope of a project, establish clear requirements, and ensure that the final product meets the needs of the users.
Acceptance criteria are typically written in a user-centric format and describe the features and functionality that the final product must have in order to be considered complete. They are usually defined before the development of the product starts, and are used as a guide throughout the development process to ensure that the final product meets the needs of the stakeholders.
Acceptance criteria are often used in conjunction with other project management tools such as user stories, use cases, and test cases to ensure that all requirements are met and that the final product is of high quality. They are also used to measure and track the progress of a project, and to establish clear milestones and deadlines for the development team.