Merge pull request #3019 from MicrosoftDocs/master

Pushing changes live

Author: KumarVivek

powerapps-docs/guidance/TOC.yml

@@ -0,0 +1,102 @@
+- name: Guidance
+  items: 
+  - name: Power Apps guidance documentation
+    href: index.yml
+  - name: Planning a Power Apps project
+    items:
+    - name: Introduction
+      href: planning/introduction.md
+    - name: Differences between Power Apps and traditional app development approaches
+      href: planning/app-development-approaches.md
+    - name: Planning phase
+      items:
+      - name: Overview
+        href: planning/planning-phase.md
+      - name: Identifying the business problem to solve (the use case)
+        href: planning/identifying-business-problem-to-solve.md
+      - name: Example - Expense reporting
+        href: planning/example-expense-reporting.md
+      - name: Understanding the current business process
+        items:
+        - name: Overview and identifying key contributors
+          href: planning/understanding-current-business-process.md
+        - name: Documenting the business process
+          items:
+          - name: What is the task?
+            href: planning/what-is-task.md
+          - name: Who is doing the work?
+            href: planning/who-is-doing-work.md
+          - name: What activities are being performed?
+            href: planning/what-activities.md
+          - name: What data is needed?
+            href: planning/what-data-needed.md
+          - name: What data is created or edited?
+            href: planning/create-edit-data.md
+          - name: What decisions, approvals, or rules are there?
+            href: planning/decisions-approvals.md
+          - name: What is the next task?
+            href: planning/next-task.md
+          - name: Visually mapping the process
+            href: planning/visually-map-process.md
+      - name: Optimizing your business process
+        href: planning/optimizing-business-process.md
+      - name: Is it worth automating this process?
+        items:
+        - name: The cost of doing nothing
+          href: planning/worth-automating-process.md
+        - name: Defining the business value of solving the problem
+          href: planning/defining-business-value.md
+        - name: Measuring success against the business value
+          href: planning/measuring-success.md
+      - name: Creating a project plan
+        items:
+        - name: Defining the app project goals
+          href: planning/defining-app-project-objective.md
+        - name: Defining the project scope
+          href: planning/defining-project-scope.md
+        - name: Prioritizing feature requests
+          href: planning/prioritizing-features.md
+        - name: Identifying project team members
+          href: planning/identifying-project-members.md
+        - name: Listing project tasks and owners
+          href: planning/project-tasks-owners.md
+        - name: Defining the project schedule
+          href: planning/defining-project-schedule.md
+        - name: Identifying the risks
+          href: planning/identifying-risks.md
+        - name: Gaining support and sponsorship from management
+          href: planning/gaining-support.md
+    - name: Designing phase
+      items:
+      - name: Overview
+        href: planning/designing-phase.md
+      - name: Conceptual Design
+        items:
+        - name: Tasks to be done in the app
+          href: planning/app-tasks.md
+        - name: Sketching the screens
+          href: planning/sketching.md
+      - name: Architectural Design
+        items:
+        - name: Where is the data?
+          href: planning/where-is-data.md
+        - name: Working with enterprise systems
+          href: planning/enterprise-systems.md
+        - name: Data modeling
+          href: planning/data-modeling.md
+        - name: Determining which type of app to make
+          href: planning/app-type.md
+        - name: Determining where to place the logic
+          href: planning/logic.md
+        - name: Securing the app and data
+          href: planning/security.md
+    - name: Making phase
+      href: planning/making-phase.md
+    - name: Testing phase
+      href: planning/testing-phase.md
+    - name: Deploying and refining phase
+      items:
+      - name: Making your app discoverable
+        href: planning/discoverability.md
+      - name: Collecting feedback and analyzing telemetry
+        href: planning/feedback-telemetry.md

powerapps-docs/guidance/index.yml

@@ -0,0 +1,72 @@
+### YamlMime:Landing
+
+title: Power Apps guidance documentation
+summary: Power Apps guidance documentation provides best practice information from the team that builds Power Apps and works with our enterprise customers. We'll and and update information as they become available. 
+
+metadata:
+  title: Power Apps guidance documentation
+  description: Provides best practice guidance information for Power Apps.
+  services: service
+  ms.service: powerapps 
+  ms.subservice: subservice
+  ms.topic: landing-page 
+  ms.collection: collection
+  author: KumarVivek
+  ms.author: kvivek
+  ms.date: 06/15/2020 
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
+
+landingContent:
+
+  # Card 
+  - title: Planning a Power Apps project
+    linkLists:
+       - linkListType: overview
+         links:
+          - text: Introduction
+            url: planning/introduction.md       
+          - text: Planning phase
+            url: planning/planning-phase.md
+          - text: Designing phase
+            url: planning/designing-phase.md
+          - text: Making phase
+            url: planning/making-phase.md
+          - text: Testing phase
+            url: planning/testing-phase.md
+          - text: Deploying and refining phase
+            url: planning/discoverability.md
+
+  # Card
+  - title: Related content
+    linkLists:
+       - linkListType: overview
+         links:
+          - text: Create apps in Power Apps
+            url: /powerapps/maker
+          - text: What are canvas apps?
+            url: /powerapps/maker/canvas-apps/getting-started
+          - text: What are model-driven apps?
+            url: /powerapps/maker/model-driven-apps/model-driven-app-overview
+          - text: Power Platform Center of Excellence (CoE) kit
+            url: /power-platform/guidance/coe/starter-kit
+          - text: Power Platform ALM guide
+            url: /power-platform/alm/          
+
+
+  # Card
+  - title: Other resources
+    linkLists:
+       - linkListType: concept
+         links:
+          - text: Power Apps licensing
+            url: /power-platform/admin/powerapps-flow-licensing-faq
+          - text: Power Apps US Government plans
+            url: /power-platform/admin/powerapps-us-government
+          - text: Power Apps Support
+            url: https://powerapps.microsoft.com/support/
+        
+          
+
+
+

powerapps-docs/guidance/planning/app-development-approaches.md

@@ -0,0 +1,58 @@
+---
+title: Power Apps vs. traditional app development approaches | Microsoft Docs
+description: Learn how Power Apps development compares to traditional app development in two key areas - how team members collaborate and the development process methodology
+author: taiki-yoshida
+ms.service: powerapps
+ms.topic: conceptual
+ms.custom: guidance
+ms.date: 06/16/2020
+ms.author: tayoshi
+ms.reviewer: kathyos
+
+---
+
+# Differences between Power Apps and traditional app development approaches
+
+Compared to traditional app development, Power Apps projects are different in
+two key areas:
+
+- How various members of the organization work together to create the solution
+
+- Development methodology
+
+## Differences in who develops the app
+
+Power Apps is a platform that benefits both "pro developers" and "citizen
+developers."
+
+In a traditional development environment, only pro developers could be involved with the
+actual making of an app. With Power Apps, everyone has the power to build
+the apps they need by using advanced functionality that was previously available only to
+professional developers. Power Apps "democratizes" the custom business app
+building experience by enabling users to build feature-rich, custom business
+apps without writing code.
+
+![Microsoft Power Platform and Azure ecosystem](media/ecosystem.png "Microsoft Power Platform and Azure ecosystem")
+
+## Differences in development methodology
+
+With traditional app development such as the "waterfall" model, where the process flows downward from the design phase through release, there's a long lead time
+before a user actually sees the working app. As a result, there's an increased risk
+that there will be gaps between what the user initially requested as a requirement and what
+the app developer created.
+
+![Waterfall development: Design, develop, test, and release](media/waterfall.png "Waterfall development: Design, develop, test, and release")
+
+Even with more modern development approaches such as agile development,
+a significant amount time can pass before the first minimum viable product (MVP) is
+delivered to users.
+
+![Agile development: Design, iterate several times, then release the first MVP](media/agile.png "Agile development: Design, iterate several times, then release the first MVP]")
+
+With Power Apps, you can quickly create a usable version of your app, because
+Power Apps provides a WYSIWYG (what you see is what you get) development
+experience. Users experience the actual working app very early in the
+development process, and if new requirements arise, new features can be added to
+the next version.
+
+![Power Apps development: Low code plus WYSIWYG allows for an MVP to be developed right away](media/power-apps-development.png "Power Apps development: Low code plus WYSIWYG allows for an MVP to be developed right away")

powerapps-docs/guidance/planning/app-tasks.md

@@ -0,0 +1,56 @@
+---
+title: Designing - Tasks to be done in an app | Microsoft Docs
+description: As part of the design phase of a Power Apps project, learn how to identify the tasks to be done in the app.
+author: TGrounds
+ms.service: powerapps
+ms.topic: conceptual
+ms.custom: guidance
+ms.date: 06/16/2020
+ms.author: thground
+ms.reviewer: kathyos
+
+---
+
+# Identifying the tasks to be done in the app
+
+To identify the tasks that are required in the app, you should refer to the
+business process flowchart that you created in the planning phase and add
+detail. Organize the information and list the tasks that are to be accomplished
+on each screen.
+
+When you write the tasks, remember to consider tasks for each persona who will
+be using the screen or app. Try to separate them into sections.
+
+Along with the tasks that users need to do, refer to your notes about what
+information is required to complete each task. That will help you define what
+information you need to store and display.
+
+If you're working with multiple people, using tools like Microsoft Planner or the
+Microsoft Whiteboard app will help you efficiently collaborate and work together on
+listing the tasks.
+
+## Example: Tasks for creating and viewing expense reports
+
+We considered the tasks done by people who will be creating and viewing the
+expense reports. We'll separately consider the tasks for approvals and for
+weekly budget reporting.
+
+![Business process flowchart with tasks for the expense report creating and viewing app](media/app-tasks.png "Business process flowchart with tasks for the expense report creating and viewing app")
+
+Based on the above, we think the expense report create/view app needs these
+screens and components:
+
+- A list of reports, with filtering
+
+- A single report view, with edit and view-only modes
+
+- Buttons in the editing view to cancel, save, and submit
+
+- Button for Accounting to use to export data
+
+- Various submit/cancel/save messages
+
+- The ability to attach a photo of a receipt and to view attachments
+
+> [!div class="nextstepaction"]
+> [Next step: Sketching the screens](sketching.md)