Software devevelopment process methodology

1. 3 Roots Studios
Process Methodology and Flowchart

2. Pre-Sales
Requirement Gathering
Update project
tracker
document
Preparing project proposal
Update project
tracker
document
Prerequisites: Design 2 generic project proposal formats based on client profile
(short and detailed). The same can be then modified and updated specifically for each projects.
Send proposal to
client
Save to Cloud
Pre-requisites:
1.Create proper contact addresses for communication with client: emailId, phone number,
Skype account etc.
2.Finalise Project tracker tools: google docs, basecamp, zoho, jira, vtiger, sugar CRM etc.
Notes:
Estimate tracker should include fields like:
Client details, person incharge, estimate details(title, devices, platforms, costing, man hours,
rate ); status(requirement gathering, estimate proposed, sign-off, kick-
off,design,development,QA,Deployed)and remarks.
Gather initial requirement from client
through email, phone, Skype, ask for a
requirement doc if possible
Prepare project
proposal
Prepare project
proposal
document

3. Project sign-off
Pre-requisites: Create a high level generic template for SOW and MSA
client
response on
proposal
Follow up & wait
+ve
-veNil
Negotiate
Notes: High level SOW should include: Project overview, features, client roles and
dependencies, risks and mitigation plan, high level timeline and project plan, deliverables,
signature of both the parties.
Prepare high
level SOW and
MSA
Update
project tracker
document(Agree
ment
submitted)
Send SOW &
MSA to client for
sign-off
Save to Dropbox
Update
project tracker
document(signe
d off
Update
project tracker
document(signe
d off)
Save signed
MSA and SOW to
Dropbox
Client signature
received on
documents
proceed to kick off
Project kick-off meeting, get licences and devices list from
client, assign resources to the project

4. Project schedule & SRS
Planning phase
Create a detailed project schedule listing out
timelines, resources, client dependencies
Prepare detailed SRS/BRD/Low level SOW for the
project including : wireframes, graphic (UI/UX)
themes and mockup screens.
Send SRS/BDR
to client and get it
signed off
Save to Dropbox
Update project
tracker document
Project resource allocation(Human resource,
Development and PM Software, Hardware)
Need a tools to be used for maintaining project schedule and resources allocation and
occupancy.
•
The high level wireframe and UI/UX mockups can be given to client in project sign-off phase
as well, based on requirement to assist in sign-off.
•
The SRS/BRD for this phase should mention in detail the complete requirement, System
overview, targeted OS, platform, devices, user interfaces; constraints, assumptions and
dependencies; Design constraints/compliances; Licensing, IP, third party integration, open
source libraries integration etc.

5. Software Design Document
Design phase
Graphics design & wireframe
Prepare Software Design Document for the project including: database
design, architecture design, interface design and procedural designs
Prepare unit test cases
and low level QA test
cases document.
Design app graphics for all screens.Update BRD with actual graphics & wireframe
Send
documents to
client and get
signed off
Save to Dropbox
Update project
tracker document
Test cases
Send
documents to
client and get
signed off
Save to Dropbox
Update project
tracker document
Send
documents to
client and get
signed off
Save to Dropbox
Update project
tracker document

6. Coding
Development phase
Divide the project into sub-modules and assign them
within team
Gather project related resources: SDKs, libraries, assets
and credentials.
Code
Test Commit
Update Tracker
and Repository
Integrate
Test
Code
review
The team leads will be responsible for creating the architecture of the project and for code review
of the code regularly to check the code structure, proper coding conventions and the architecture.
•
Developers will be responsible for regular update of source code into version control repository.
Send weekly stats report to client

7. QA
Testing $ Deployment
Share QA
Report and
build with
client
Execute test
cases
Report bugs
using bug
tracker tools
Generate QA
Report
Bug fixing
Verification
Regression
testing
QA Cycle
Implement
client
feedbacks
Client
feedback and
approval
Approved
Implement client
feedbacks
Not approved
Deploy

8. Maintain an app Dashboard with all the details of finished projects including : total time and
effort the project took, payment details, resources worked under it, technology used, platforms
targeted, case study, client response, reusable components and lessons learnt
•
Before deploying the app recheck the source code and graphics for IP and third party components .
Deployment
Deploy app to store Submit code to client Sign-off document
Update project
tracker

9. Tools
Tools & Sheets
Cloud Storage : Dropbox, google drive, iCloud
Code sub versioning : Unfuddle, bitbucket,github
Project schedule tracker : google sheet, open project
Bug and issue tracker : Bugzilla, Unfuddle
Project management tool : Unfuddle, Jira
Pre sales tracker : Zoho, google sheets
Resource tracker(Resource planning and forecasting) : google sheets
Project Dashboard(project summary, case studies, technologies used, resources, reusable
components, lessons learnt) : google sheets
Resource tracker(Resource planning and forecasting) : google sheets

10. Thank You