Skip to content

Latest commit

 

History

History
62 lines (36 loc) · 5.12 KB

Shantagouda Kuntoji Project Log (Respect).md

File metadata and controls

62 lines (36 loc) · 5.12 KB
Raw

Shantagouda Kuntoji Project Log (Respect)

This Wiki page contains information about how team implemented LEAN value 'Respect' during each week

Whats is Respect in Extreme Programming (XP) ?

Respect in Extreme Programming (XP) refers to a system where everyone gives and feels the respect they deserve as a valued team member. Everyone contributes value even if it's simply enthusiasm. Developers respect the expertise of the customers and vice versa. Management respects our right to accept responsibility and receive authority over our own work.

Week 1 :

  • Team Sparks had their first team meeting this week. Since we all are new members in team , we introduced ourselves and it was evident that all team members respects each other and considers themselves as the valued team member.

  • Individual Contribution to team was discussed and everyone's views were taken and respected.

  • Team has vast resource pool in terms of technical expertise, team members respected everyone's technical expertise and took relevant information regarding technologies they will be using in the project.

Week 2 :

  • This week team had discussion about basic functionality of the application. Everyone had fair chance to express their ideas about the how the application functions.

  • All the ideas were heard from team and elaborate discussion was done about these ideas. This activity was vital as to see every team member as valuable contributor and respect their idea.

  • Team unanimously agreed to take in the ideas that best suited fot the application. Sense of respect to other individuals and their ideas was maintained by all team members.

Week 3 :

  • This week team discussed about the functionality interaction within the application. Dependencies of the application on other modules were discussed. Each member expresses his functionality and the dependencies he will be having within the application.

  • Team decided to make few changes as per the requirmeent and dependencies of the other team members. Team ensured that all the dependencies are taken care and wherever possible changed few functionalities with the consent of team memebr concerned.

  • Utmost respect was maintained for team members idea and their functionality dependencies, which will help to achieve great results as a Team. Changes to functinalities were only done with the consent of concerned team member.

Week 4 :

  • This week we discussed about web services development and it's status in different modules. We also discussed about front-end technology to be used for the project.

  • Everyone gave their front end decvelopment ideas and we all agreed to use AngularJs as user interface technology for our project. Everyone was given the proper respect and their ideas were discussed with pro/cons of using them.

  • Since we were in fourth week of project, we agreed to accelarate the projects works and finish the web services part in this week. Respect to other team members was maintaind at all the phases of discussion.

Week 5:

  • Team had discussion about connecting backend to frontend technology. JQuery will be used to implement UI. Everyone's views were considered while deciding about UI framework.

  • This week team will be working on running DB's on aws. We had good discussion about that. All the queries and clarification of team were discussed and utmost respect was maintained for other team members in the process.

  • As just four weeks are left to finsih the project, we decided to fasten our works. In all the processes, respect towards other members was maintained.

Week 6:

  • This week team worked towards finishing the web services development. Elaborate discussion was done on blockers and challenges of developing web services. All the team members took part in discussion and all the views and ideas were respected.

  • This week team has set target to deploy the applications to AWS. We discussed about the procedure to deploy to AWS. all the queries related to this were clarified within team.

  • Team respected other individuals and their ideas. All the team members were given fair time to explain their ideas and views about the next steps in project.

Week 7:

  • This week team worked on deploying their application to AWS. Challenges and drawbacks were discussed and everyone took active part in the discussion.

  • We also discussed about the partition tolerence that we have to demonstrate in the demo and everyone's views were respected and received.

  • Team respected other members ideas and changes were advised to team members where ever possible. Respect towards others was maintained at all the stages.

Week 8:

  • Since this was the last week of project, we focussed on integration and testing of application. We checkd about the AWS Deployment of applications and databases. All the team members took part in this process.

  • We also discussed about partition tolerance and checked the various ways in which we can show the partion tolerance of all the modules of application.

  • Team members respected other ideas and views. Team ended the meeting with succussful running of application and this was mainly possible because all the team members listened to other views and ideas.