Power Apps T-Shirt Size Implementation Model: 1-Month Implementation

EPAM recommends using a T-shirt approach to estimate Power Apps project duration, team composition, and efforts based on project size (S, M, L) and form customization. Agile methodology is used for delivery with detailed release planning and regular sprints.

###Delivery outcomes per project size:

Small (S): *Base wireframes; *Base solution design; *Imported data; *Source code; *Base User stories; *A solution built through iterative development of its components, such as user interface forms, automated workflows, data storage systems, configured connectors, integrations, extensions, dashboards, reports, security roles, among others.

Medium (M): *Features roadmap; *Project governance; *Base wireframes; *Solution architecture; *Deployment strategy; *Configured environment; *Imported data; *Software documents; *Source code; *User stories; *Test cases; *A solution consisting of various components that are incrementally developed, such as UI forms, automated workflows, data storage mechanisms, configured connectors, integrations, extensions, dashboards, reports, security roles, and more.

Large (L): *Project Plan; *Risk mitigation plan; *Project governance; *Base wireframes; *Solution architecture; *Deployment strategy; *Configured environment(s); *Imported data; *Software documents; *Source code; *User stories; *Test cases; *Automated test scenarios; *Solution with elements as developed increments (e.g. UI forms, automated flows, data storage, configured connectors, integrations, extensions, dashboards, reports, security roles, etc.)