Task 6 - Project Management Tool - JIRA

Q1)

Jam0003/Guvi-Jira

Q2)

Jam0003/Guvi-Jira

Q3)

1. Sprint Planning:

   • Plan sprints (time-bound iterations) based on the backlog.

   • Assign tasks to each sprint.

   • Prioritize tasks based on importance and dependencies.

   • Example:

     • Sprint 1: Authentication (registration, login).

     • Sprint 2: Account management (view details, update info).

2. Sprint 1 Execution: Develop login and account management functionality

   Task 1: Design and implement user registration form

   • Developers design the form UI and implement backend validation logic.

   • QA tests the form to ensure it captures required user details and validates inputs.

Task 2: Implement backend logic for user registration

• Backend developers create API endpoints to handle user registration requests.

• Unit tests are written and executed to verify the registration logic.

Task 3: Create frontend login page

• Frontend developers design and implement the login page UI.

• Integration with backend authentication services is established.

Task 4: Implement login authentication

• Backend developers implement authentication logic using username/password.

• Integration tests are conducted to ensure successful authentication.

Task 5: Develop password reset functionality

• Developers create a password reset flow, including UI and backend logic.

• QA verifies that users can reset passwords securely.

Task 6: Design account overview page

• UI/UX designers create wireframes and designs for the account overview page.

• Feedback is gathered from stakeholders and adjustments are made as necessary.

Task 7: Fetch and display account balance

• Backend developers integrate with banking APIs to retrieve account balance data.

• Frontend developers display the balance information on the account overview page.

Task 8: Display recent transactions

• Backend developers fetch recent transaction data from the database or external APIs.

• Frontend developers present transaction history in a user-friendly format.

Task 9: Add functionality to download account statement

• Developers implement a feature to generate and download account statements.

• QA ensures that statements are generated accurately and securely.

Task 10: Allow users to update contact information

• Developers create forms for users to update their contact details.

• Validation is applied to ensure data integrity.

Sprint Review: Sprint 1

During Sprint 1, the focus was on implementing basic user authentication and account management features. Let's review the progress made:

1. Implemented user registration form: Completed

Users can register for an account with their personal details.

2. Backend logic for user registration: Completed

Backend functionality to process and store user registration data.

3. Created frontend login page: Completed

Users can access the login page to enter their credentials.

4. Implemented login authentication: Completed

Users can log in securely using their credentials.

5. Developed password reset functionality: Completed

Users can reset their password if forgotten.

6. Designed account overview page: Completed

Initial design for displaying account balance and recent transactions.

7. Fetched and displayed account balance: Completed

Users can view their account balance upon logging in.

8. Displayed recent transactions: Completed

Users can see their recent transactions on the account overview page.

9. Added functionality to download account statement: Completed

Users can download their account statement in PDF format.

10. Allowed users to update contact information: Completed

Users can update their contact information associated with their account.

Overall, all planned tasks for Sprint 1 have been successfully completed. The team has made good progress and delivered the expected functionalities.

No changes are required to the project plan based on the completed tasks. The project is on track, and we will proceed with Sprint 2 as per the original plan.

The daily Scrum meeting, also known as a daily stand-up, the team typically gathers to discuss their progress, plans for the day, and any impediments they're facing. Here's how such a meeting might go (Example)

Time: 9:00 AM

Duration:15 or 20 minutes

Participants:

1.Product Owner

2.Scrum Master

3.Developers

4.Testers

5.Operations Team

Agenda:

1. What has been done since the last meeting?

Each team member briefly shares the tasks they completed yesterday.

2. What will be done today?

Each team member discusses their plan for the day and the tasks they intend to work on.

3. Are there any blockers or impediments?

Team members highlight any issues they're facing that are hindering their progress.

The Scrum Master takes note of these blockers and works to resolve them after the meeting.

Example Daily Stand-up Meeting:

ScrumMaster: Good morning everyone, let's start our daily stand-up meeting. What tasks have you completed since yesterday?

Developer 1: I finished implementing the login authentication feature.

Developer 2: I completed the frontend design for the account overview page.

Tester: I conducted testing on the user registration form and found a few minor issues that need to be fixed.

Operations Team: We've deployed the latest bug fixes to the staging environment for testing.

Scrum Master: Great progress, everyone! Now, what are your plans for today?

Product Owner: I'll be reviewing the frontend designs and providing feedback.

Developer 1: I'll start working on the password reset functionality.

Tester: I'll continue testing the login authentication feature and address the issues found earlier.

Operations Team: We'll monitor the deployment process and ensure a smooth transition to production.

Scrum Master: Excellent. Lastly, does anyone have any blockers or issues?

Developer 2: I'm blocked on accessing the required API documentation for integrating external bank APIs.

Scrum Master: Thanks for bringing that up. I'll follow up with the necessary stakeholders to unblock you. Let's wrap up the meeting now and address any further issues afterward.

Conclusion:

Daily stand-up meetings like this help keep the team aligned, ensure transparency, and enable prompt issue resolution, fostering a collaborative and efficient work environment.

Sprint Retrospective: Sprint 1

What went well:

1. Completion of planned tasks: All the tasks planned for Sprint 1 were successfully completed within the allocated time frame.

2. Effective communication: Daily stand-up meetings facilitated clear communication among team members, helping to address issues promptly.

3. Collaboration: Team members collaborated well, supporting each other to overcome challenges and deliver the required functionalities.

4. Quality of work: The delivered features met the acceptance criteria and demonstrated good quality in terms of functionality and usability.

Areas for improvement:

1. Documentation: Documentation regarding the implemented features and code could be more comprehensive to aid in future reference and maintenance.

2. Testing coverage: While testing was conducted, there is room for improvement in increasing the depth and coverage of testing to catch more edge cases and potential bugs.

3. API integration: Better coordination is needed with external stakeholders to streamline the process of accessing API documentation and integrating external bank APIs.

4. Time estimation: Some tasks took longer than initially estimated, leading to a tighter schedule toward the end of the sprint. Improved estimation practices could help in better planning for future sprints.

Action items for next sprint:

1. Enhance documentation practices to ensure comprehensive coverage.

2. Increase testing coverage and rigor to catch more potential issues.

3. Improve coordination with external stakeholders for smoother API integration.

4. Refine task estimation techniques to better manage the sprint timeline.

Conclusion:

Overall, Sprint 1 was successful, with the team delivering all planned features effectively. By addressing the identified areas for improvement, we aim to further enhance our efficiency and productivity in the upcoming sprints.

Release Planning: Net banking App

First Release Features and Functionalities:

1. Authentication and User Management: Allow users to register for an account and log in securely.

2. Account Management: Enable users to view account balance, recent transactions, and update their profile information.

3.Transaction History and statements: Provide users with access to their transaction history for a specified period.

4. Fund Transfers and payments: Implement the ability for users to transfer funds between their own accounts and to other accounts within the same bank.

5. Security and alerts: Implement basic security measures such as encryption for transactions and password reset functionality.

Timeline for First Release:

Week 1-2: Develop and test user registration, authentication, and account management features.

Week 3-4: Implement and test fund transfer functionality along with basic transaction history.

Week 5:Finalize security features and conduct thorough testing to ensure robustness.

Week 6:Prepare documentation, user manuals, and conduct user acceptance testing (UAT).

Week 7:Address any final issues or bugs identified during UAT.

Week 8:Release the first version of the net banking app to users.

Key Considerations:

The release timeline may vary depending on the complexity of features and the team's capacity. Continuous integration and deployment practices should be followed to ensure regular updates and improvements after the initial release. Feedback from users should be collected and incorporated into future releases to enhance the app's usability and functionality. By following this release plan, we aim to deliver a functional and secure net banking app to users within an 8-week timeframe, focusing on essential features for an effective first release.

Roles Involved in Scrum:

Product Owner

The Product Owner represents the stakeholders and is responsible for maximizing the value of the product. They prioritize the backlog, ensure clear communication of requirements, and accept completed work.

Business Analyst

The Business Analyst works closely with the Product Owner to analyze business needs, gather requirements, and translate them into user stories. They assist in defining the scope of the project and ensuring alignment with business goals.

Managers

This category can include various managers such as project managers, Scrum Masters, or team leads. They facilitate the Scrum process, remove impediments, and support the team in achieving its goals.

Tech Architect

The Technical Architect provides technical guidance and ensures the overall architecture of the solution aligns with the project's requirements and long-term goals. They collaborate with the development team to design robust and scalable solutions.

Development Team

The Development Team consists of cross-functional individuals responsible for delivering increments of potentially shippable product at the end of each Sprint. They collaborate to design, develop, and test features based on the user stories.

Testing Team

The Testing Team, also known as Quality Assurance (QA), is responsible for ensuring the quality of the product by conducting various types of testing such as unit testing, integration testing, and acceptance testing. They work closely with the development team to identify and resolve defects.

Operations Team

The Operations team manages the deployment, monitoring, and maintenance of the product in production. They ensure the stability, reliability, and performance of the system and may also be involved in infrastructure setup and configuration management.