SOP for Mobile Team

Standard Operating Procedure (SOP) for Mobile Team

• SOP is a set of step-by-step instructions for employees to execute routine operations.
• It aims for efficiency, quality output, and uniformity of performance, reducing miscommunication and compliance issues with industry regulations.
• SOPs can consist of steps for achieving a quality goal or could have sub-procedures with steps of their own.

Document History

• Standard Operating Procedure Number: F_ETPL_MOBILE_01
• Revision Number: 0
• Created Date: 01-01-2023
• Prepared By: Ahmad Palsaniya
• Updated Date: 12-10-2023
• Approved By: Ahmad Palsaniya

Purpose

• SOP is a set of step-by-step instructions for employees to execute routine operations efficiently and uniformly.
• It aims to achieve high quality output while preventing industry-standard compliance problems.

Related Standards and Procedures

3.1 Planning: Define Goals & Application Specification

• Gather detailed info on app functionality, features, screens, custom designs, and development work.
• Discuss app requirements with client.
• Define visual style, personality, and basic layout.
• Create a high-level sitemap with a mockup navigation menu.
• Create a low-fidelity wireframe of important screens (dashboard, CMS).
• Conduct detailed research on any other key screens.
• Create basic mockups.
• Suggest the best state management for the application.

3.2 Design & Production: Design Logo

• Create a logo if the client doesn't provide one.
• Determine if a logo design is required or if a logo image can be provided by the client.

3.3 Design & Development: Create UI UX Design

• Option to create a new UI/UX or customize an existing one with client logo and design preferences.
• Specify the package name format for new projects, omitting Elsner's name in project names.
• Use the Latest and Stable SDK version.
• Create UI/UX mockups for the screens with client logo, color scheme.
• Get client feedback on UI/UX.
• Design secondary page mockups (CMS, product listings, product details).
• Get client approval for UI/UX designs.
• Demonstrate completed work to the client.
• Use version control systems (git, bitbucket) for code management.
• Add comments and improve code reusability.
• Design controllers without database logic.

3.4 Design & Production: Setup Project and structure

• Set up project structure using a third-party library.
• Implement business logic on the screen.
• Choose a framework for differentiating between business logic and design.
• Use libraries for server connections.
• Utilize Firebase for push notifications.
• Manage error handling for network connections and API responses.
• Use MVC or MVVM structure for the application.
• Ensure 3rd-party classes are from trusted sources with no vulnerabilities.
• Convert 3rd-party classes to libraries where appropriate.
• Compress all uploaded images.
• Hide directory listings for all folders.

3.5 Testing & Feedback

• Development review site for functionality, ASO (app store optimization), and design issues across various devices.
• Evaluate screen content, text, and image issues for consistency and readability across devices.
• Conduct app review for ASO issues.
• Obtain testing release notes from the tester. Verify app build success or identify bugs.

3.6 Post-Development & Launch

• Obtain application upload details (Title, description, logo, banners, screenshots, email, privacy URL) from client.
• Use a live domain for API URLs.
• Post-launch monitoring for 48 hours (check for issues).
• Address any issues from Google or Apple.
• Maintain code backups on GitHub.

4. Kick-off Meeting

• Conduct kickoff meetings for new projects.
• Discuss project flow and address any questions.

5. Roles and Responsibilities

• Collaborate with product managers, designers, and backend developers to design, develop, and deliver mobile applications.
• Develop high-quality mobile apps using Swift, Objective-C, Java, Kotlin, Dart, or React Native.
• Ensure writing code that's clean, maintainable, and understandable by other team members.
• Use version control tools (like Git) to manage and maintain code repositories.
• Integrate APIs and backend services with mobile applications.
• Write automated tests to enhance application quality and stability.
• Fix bugs and troubleshoot issues promptly.
• Optimize app performance, battery life, and user experience.
• Keep updated on the latest in mobile development trends and technologies.
• Collaborate to ensure consistency in development standards.
• Collaborate with designers to align user interfaces and experiences with user needs.
• Adhere to industry standards and best practices for security and data privacy.
• Maintain code documentation.
• Work with QA teams to ensure functional and performance requirements.
• Communicate project progress with stakeholders and team members.

6. Dedicated Developers SOP

• Dedicated developers should adhere to a separate SOP in addition to standard procedures.

7. Developer Release Note

• Create developer release notes for QA testing builds.
• The release build format should match a given format.

8. Daily Work Reporting

• Employees should submit daily work reports using two methods.

8.1 PMS Work Reporting:

• Employees daily must enter timesheet in the Proof Hub (PMS).
• Log project activity durations.
• Record and upload hours worked per task.
• Request task assignment from PM/TL if no tasks are available.
• Log a minimum of 8.5 hours for full day and 4.5 hours for half a day.

8.2 Sheet Work Reporting:

• Employees must enter daily timesheet in a sheet provided by the TL.
• Log project activity durations.
• Log hours worked per task as tasks are completed

9. HRMS Reporting:

9.1 Daily In-Out

• Daily in-out is mandatory for all employees and for Mobile Developers.
• Use the correct HRMS credentials for daily in-out record entries.
• Use the employee symbol in the left sidebar to select "My In-Out"sub-menu.
• Employee presence is digitally recorded and updated.

9.2 Leave Application

• Employees request personal, half-day, or flexi leaves through HRMS.
• Use the "Leave" tab found in the left sidebar menu, and use the "Leave Application" tab.
• Specify the requested leave type, duration, reason, etc. and submit the request.
• Check and verify leave status on the leave page.

9.3 Work From Home Application (WFH)

• Request WFH using the HRMS "Work From Home" tab to apply for remote work.
• Select the application type and specify the needed WFH dates & reason.
• Complete and submit requests via the WFH application form.
• Check leave status on the appropriate dashboard page.

10. Onboarding of a New joinee 2-5 day Technical Plan & Q&A

• Onboarding includes a 2-5-day technical plan with HR formalities and meetings for onboarding and education.
• The plan has multiple stages.
• The new joinee is responsible for achieving an assessment score of 95%.

11. Conclusion

• The SOPs are meant to improve developer work quality, accessibility and understanding by other developers.

This quiz covers the Standard Operating Procedure (SOP) for the mobile team, detailing the steps required for efficient operations. Participants will learn about the purpose, document history, and related standards to enhance compliance and output quality in routine tasks.