Implementing a development methodology on DevTeam

Development
1

To initiate a discussion on the above topic; me, @Gravewalker, and @YohanAvishke had a brainstorming session on 2020-12-10T18:30:00Z. Here are the ideas we came up with.

  • Decrease the expected working hours per week to 4 hours. This will be taken as a key unit when planning.
  • Had a discussion on the Scrum framework
  • Use the Prototype Method to maintain the SDLC while running sprints on each prototype iterations.
  • A sprint would have an average of 2 weeks duraion.
  • Use GitHub project boards to handle sprints. 1 sprint = 1 board

Cameup with a rough backlog of scholarX:

 1. User authentication
	1.1. Kubernetes cluster configuration 
	1.2. API gateway
	1.3. Frontend Token handling 
	1.4. Sign in UI
	1.5. Log in UI
	1.6. Logout button in UI
	1.7. User authentication backend application
		1.7.1. Linkedin authentication
		1.7.2. Introspecture API
2. New program state
	2.8. Backend 
		2.8.1. Validate existing APIs and fix issues
	2.9. Frontend
		2.9.1. Fix change state UI
		2.9.2. Selection UI
			2.9.2.1. Basic UI with mentor listing
				2.9.2.1.1. List mentors
				2.9.2.1.2. Create sub view for the users who don't have access
			2.9.2.2. Actions
	2.10. Testing the new program state 
	2.11. Find exisiting bugs on the application and create issues
3. Backend test case review
4. Backend bug fixes
5. UI Bug fixes
	5.1. Testing
6. Rearrange the home
7. UI consistency 
8. Email configuration
9. Readme files 
10. Create a repo to host static pages (for programs)
	10.1. Create a subdomain and deploy on GH pages

More details of the frontend backlog can be found here:
Improving the ScholarX platform frontend

  • The current prototype is to have an application that is capable of running the complete lifecycle with user authentication. The delivery date will be on the 13th of March 2021. (@akshika47, @Minuri_Adasuriya, @Saumiyaa_P1 )

  • New program state implementation was selected as the initial sprint. Sprint duration will be 2 weeks. The goal is to release a minor release with the new program state.

      2.8. Backend - Piumal
  	2.8.1. Validate existing APIs and fix issues
  2.9. Frontend
  	2.9.1. Fix change state UI - Gimhan
  	2.9.2. Selection UI - Anjula
  		2.9.2.1. Basic UI with mentor listing
  			2.9.2.1.1. List mentors
  			2.9.2.1.2. Create sub view for the users who don't have access
  		2.9.2.2. Actions
  2.10. Testing the new program state 
  2.11. Find existing bugs on the application and create issues - Milukshan

Above is a brief overview of the call. Let’s extend the discussion on today’s standup!

1 Like
2

Hi team, the delivery date is problematic :(. According to this, we won’t be able to use this for the current ScholarX program, right?

Therefore, we need a plan to run SX21. My suggestion is to run a parallel thread to update the static website and assign someone to coordinate with the program management team. We can run the program as we did last year.

3

Hi @akshika47,

The deadline defined considering the tasks needed to be done, and available resources with a buffer. One of the things that we can do to speed up is get involved more developers. However, having a plan to run ScholarX as we did before is a good idea because we might end up in trouble if we try to run it on an unstable application.

4

No point running an unstable version. So let’s stick to last year’s method.

1 Like
5

great! @Dilshan_Naveen @NaviRocker, one of you like to lead the ScholarX 2021 page?
@Janeth_Fernando and me there for your help!

6

I’m up for the challenge with your help @jaye @Janeth_Fernando

1 Like
7

That’s awesome @NaviRocker!!! :heart_eyes:

All you have to do is to coordinate with @Dharana_J and the ScholarX team through the program and do the relevant updates to the ScholarX page. I’ll add you to the sx-planing slack channel.
You have to report your work to @Janeth_Fernando.

Feel free to contact Janeth or me at any time via Slack/Hive/messenger! :hugs:

1 Like
8

@jaye, can I contribute as well?

1 Like
9

Absolutely yes!! Get in touch with @Dilshan_Naveen and @Janeth_Fernando

1 Like