An attempt to answer one question which all people trying to pick a front end framework has . Is Angular or React the right choice ? Angular vs React is a burning adoption question on most Project planning sessions and one which often a developer has to confront. React is a Facebook supported initiative and is a javascript library . It would be wrong to call it a framework based on its initial release versions . It helps to create resusable components in applications and is javascript based . Angular has equally competent heritage from Google .With Angular being a new version to previous Angular JS which was widely successful. Angular has now ditched Javascript and adopted Typescript , i was very skeptic of this choice especially typescript being previously unknown in the front end developer circles . Once I started using Typescript I could see some clear advantages and choice for strong typing which was missing in Javascript for long was being enforced. Of course I
I had to create a project management practice in Agile for one of my projects.
I had experience in working with Scrum and Scrumban Agile methodolgies .
I decided to adopt Scrumban as i found it better that Scrum and more suited for product development with uncertain requirements and often user stories which require a depeer research and understanding .
You can read on further from the links below on Scrumban
https://www.agilealliance.org/what-is-scrumban/
http://leansoftwareengineering.com/ksse/scrum-ban/
I had to choose a tool that was open source and readily available , I evaluated the below tools
Of the above I found Asana highly suitable and configurable and bingo they also had a mobile application which was quite user friendly.
The Sprints were planned for 2 weeks duration and a Milestone of 1 month duration
. Each Milestone had two Sprints .
For scrumban I choose the below project structure
Here the Backlog had the backlog items identified for the sprint and the Milestone .
The tags option is used to denote the epics of the story .We had two projects "Dashboard" and "Campaign".
Now once the tasks were ready for the sprint they were moved to Sprint backlog
Suppose its Sprint 1.1 of the First Milestone
The tasks will be ordered in 4 categories
In the Sprint planning session each tasks will be allocated story points and alloacted to a person .The story points had to be marked with "[ ]" as Asana doesnt offer a story point option for free users .
Once the tasks are completed and the "sprint is Over" they are moved to the respective Milestones for delivery
So here suppose Sprint 1.1 tasks have been completed they tasks are moved to Milestone 1 for delivery .
This is a simple way to use Asana to manage your Agile project in Scrumban .
You can refer to the official version of using the kanban board here .
https://blog.asana.com/2016/11/introducing-boards/
I have used a Custom template for plotting the Sprint burndown . You can download it here .
https://www.smartsheet.com/agile-project-management-excel-templates#agile-sprint-backlog-with-burndown-chart-template
I had experience in working with Scrum and Scrumban Agile methodolgies .
I decided to adopt Scrumban as i found it better that Scrum and more suited for product development with uncertain requirements and often user stories which require a depeer research and understanding .
You can read on further from the links below on Scrumban
https://www.agilealliance.org/what-is-scrumban/
http://leansoftwareengineering.com/ksse/scrum-ban/
I had to choose a tool that was open source and readily available , I evaluated the below tools
Of the above I found Asana highly suitable and configurable and bingo they also had a mobile application which was quite user friendly.
The Sprints were planned for 2 weeks duration and a Milestone of 1 month duration
. Each Milestone had two Sprints .
For scrumban I choose the below project structure
Here the Backlog had the backlog items identified for the sprint and the Milestone .
The tags option is used to denote the epics of the story .We had two projects "Dashboard" and "Campaign".
Now once the tasks were ready for the sprint they were moved to Sprint backlog
Suppose its Sprint 1.1 of the First Milestone
The tasks will be ordered in 4 categories
- Sprint backlog
- Ready to do
- In Progress
- Done
In the Sprint planning session each tasks will be allocated story points and alloacted to a person .The story points had to be marked with "[ ]" as Asana doesnt offer a story point option for free users .
Once the tasks are completed and the "sprint is Over" they are moved to the respective Milestones for delivery
So here suppose Sprint 1.1 tasks have been completed they tasks are moved to Milestone 1 for delivery .
This is a simple way to use Asana to manage your Agile project in Scrumban .
You can refer to the official version of using the kanban board here .
https://blog.asana.com/2016/11/introducing-boards/
I have used a Custom template for plotting the Sprint burndown . You can download it here .
https://www.smartsheet.com/agile-project-management-excel-templates#agile-sprint-backlog-with-burndown-chart-template
Great blog !! thanks for sharing the Valuable information .
ReplyDeleteMean stack online training
Mean stack training in hyderabad
Good blog !! thanks for sharing the Valuable information .
ReplyDeleteFull Stack Training in Chennai | Certification | Online Training Course| Full Stack Training in Bangalore | Certification | Online Training Course | Full Stack Training in Hyderabad | Certification | Online Training Course | Full Stack Developer Training in Chennai | Mean Stack Developer Training in Chennai | Full Stack Training | Certification | Full Stack Online Training Course