Project management-practices
Upcoming SlideShare
Loading in...5

Project management-practices



project development and management practices followed at Radix for transparency.

project development and management practices followed at Radix for transparency.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Project management-practices Project management-practices Presentation Transcript

    • Page 1
    • Project Initiation Process RSS – Resource Scheduling SystemRedmine – Project Management System Communication Monitoring & Control Project Closure Process Radix Development Methodology Annexure: Images Contact Us Page 2
    • 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
    • Projects & Operations executive registers the project into RSSProject identifiers like Project Name, Project Code, Project Technology, Project Head, and Start & End Dateare enteredProject Type (fixed, monthly, etc) is defined & project hours are allocatedProject Code is used to track the progressProject Lead/Manager uses RSS to book hours for resources/developers assigned to the projectHours are booked in RSS for month, resource, and dateProjects & Operations executive compares RSS booked hours (planned hours) with actual hours entered inRedmine and identifies discrepanciesAppropriate action is taken to mitigate these discrepancies in hours planned and actually spent Page 4
    • We manage all our projects through RedmineRole based access is given to project team membersWe 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 documentsRedmine also has User Dashboard, My Page, My ToDo, Forums, Wikis, NewsRedmine 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
    • 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 communicationConference call using Skype or GoToMeeting • Call recording in MP3 Skype Recorder • Documenting & publishing minutes of meetingPeriodic reporting on projects • Weekly status of project tasks • Tasks planned for the next week • Open items or tasks in progress Page 6
    • 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 statusProject 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
    • 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 serviceLessons 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
    • 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 clientPlanning 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
    • Page 10
    • Page 11
    • Page 12
    • Page 13
    • Page 14
    • Page 15
    • Page 16
    • Page 17
    • Page 18
    • India Office30/B Adarsh Society,Near Kaashi Parekh Complex,Swastik Char Rasta, C G Road,Ahmedabad-380009 Gujarat -India,Phone : +91-79-32403371VoIP : +1-718-715-1551Email : Page 19