The document outlines Radix Development Methodology which includes a project initiation process involving internal kick-off meetings, project registration, and formal introductions. It also describes communication through a project email group, monitoring progress using Redmine and Resource Scheduling System, conducting project closure activities like collecting feedback and documenting lessons learned. Contact details are provided at the end.

1. www.radixweb.com Page 1

2. Project Initiation Process
RSS – Resource Scheduling System
Redmine – Project Management System
Communication
Monitoring & Control
Project Closure Process
Radix Development Methodology
Annexure: Images
Contact Us
Page 2

3. Internal Kick Off Meeting
• Meeting between sales & development team
• Discussion on project requirements, milestones, technical aspects, & expected
results
Project Registration
• Project code generation
• Project update in Resource Scheduling System & Redmine
Formal Introductions
• Introduction of stakeholders
• Discussion on project objectives & expectations
• Setting up GoToMeeting & Skype conferencing
Project Email Group
• Creating single email ID for communication
• Adding email IDs of all stakeholders to group email ID
• All communication conducted & tracked through this project email group
Page 3

4. Projects & Operations executive registers the project into RSS
Project identifiers like Project Name, Project Code, Project Technology, Project Head, and Start & End Date
are entered
Project Type (fixed, monthly, etc) is defined & project hours are allocated
Project Code is used to track the progress
Project Lead/Manager uses RSS to book hours for resources/developers assigned to the project
Hours are booked in RSS for month, resource, and date
Projects & Operations executive compares RSS booked hours (planned hours) with actual hours entered in
Redmine and identifies discrepancies
Appropriate action is taken to mitigate these discrepancies in hours planned and actually spent
Page 4

5. We manage all our projects through Redmine
Role based access is given to project team members
We perform below activities in Redmine
• Define milestones & project versions
• Assign tasks to resources
• Log details of time spent
• Track progress made
• Track issues & change requests
• Manage project documents
Redmine also has User Dashboard, My Page, My ToDo, Forums, Wikis, News
Redmine features Software Configuration Management system:
• Integrated SVN to manage source code
• Source code can be managed for different project versions
• Developers commit code in SVN on task completion
Page 5

6. We conduct all communication through Project Email Group
• Group members include customers, project manager, project lead, project coordinator
• All email IDs are included in project email group
• All members can witness and track communication
Conference call using Skype or GoToMeeting
• Call recording in MP3 Skype Recorder
• Documenting & publishing minutes of meeting
Periodic reporting on projects
• Weekly status of project tasks
• Tasks planned for the next week
• Open items or tasks in progress
Page 6

7. Project Health Monitoring
• Project manager reviews the progress made on the project
• He mitigates the difference between hours planned for the project and actual hours spent
• He ensures that the project is completed and delivered on time
• Quality checks are carried out as part of quality control process
• Issues are identified and addressed proactively
• Change requests are managed effectively
• Clients are kept updated on project status
Project Documentation
• Folder management for easy classification & access to project documentation
• Documentation received from client managed under “client provided” category
• Technical documentation managed under “technical documentation” category
Page 7

8. Client Feedback
• On project completion, client feedback sheet is exchanged for comments
• Comments are invited for overall project execution, satisfaction level, & service quality
• Feedback is collected on how to further improve our performance and service
Lessons Learned
• Learnings acquired are discussed during team meetings
• Brainstorming to find out what could have been
done better
• Document the findings and learnings for future
projects
Page 8

9. Discovery Support
• Gather the requirements in detail in order to • Fix any issue reported by the client or internal
avoid gaps and meet client’s expectation QA team
• Analysis the requirement and finalized the • Support post deployment for any technical bugs
development approach. or errors
• Determine and confirm priorities with the client
Planning Implementation
• Identify the Project’s milestones and • Execute project based on the Schedule
deliverables • Monitor and controlling development activities
• Risk Analysis to make sure quality of deliverables
• Plan the Quality requirements , Plan the • Keep client updated with project progress.
Communication between different stakeholders Weekly status reports will be send to client
• Schedule the development activities based on • Demo the deliverables to the client
the scope and priorities
Page 9

10. Page 10

11. Page 11

12. Page 12

13. Page 13

14. Page 14

15. Page 15

16. Page 16

17. Page 17

18. Page 18

19. India Office
30/B Adarsh Society,
Near Kaashi Parekh Complex,
Swastik Char Rasta, C G Road,
Ahmedabad-380009 Gujarat -India,
Phone : +91-79-32403371
VoIP : +1-718-715-1551
Email : sales@radixweb.com
Page 19