Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Mendix Intermediate
True Collaboration
| Question | Answer |
|---|---|
| What Are the 5 Scrum Team Values? | Focus, Courage, Openness, Commitment en Respect |
| Focus | Breaking app in smaller sprints and limiting the flow of work into those Sprints, |
| Courage | the team has take on greater challenges than they would as individuals |
| Openness | regular reviews with stakeholders and regular planning and communication with their peers |
| Commitment | Scrum teams takes a specific amount of work being done in each Sprint. This builds trust with the stakeholders. |
| Respect | enabling openness in communication, so each team member feels safe to share their impediments, and the team can help each other with these impediments. |
| Product Backlog Refinement | Reach a mutual understanding of user stories selected Prevent how various parties interpret the stories PO will re-prioritize if needed. -> can change if there are emergency items |
| How can Story Points be determined? | by details of The user story, the Definition of done and Acceptatiecriteria |
| Sprint planning | collaborative process involving the Scrum Master, the Product Owner, and the entire Development Team. |
| Responsible PO during Sprint Planning | clarify Product Backlog items and clear goal and focus for Sprint |
| Team Velocity | The factor that determines how much a team is capable of accomplishing during one Sprint -> so they know how many user stories they can cover in a Sprint |
| What can change the Team Velocity? | Changing the Team Composition |
| Sprint Review | End of Sprint. Demonstrate the result of the Sprint to the PO / Management and End users |
| During the Demo | Acceptance criteria are used to check whether the presented increment satisfies the Definition of Done |
| Feedback received from the PO and another stakeholder may result | in a new user story added in the next Sprint, or the Product Backlog may need to undergo some adjustments. |
| Daily Scrum Questions | -What have I done since the last daily scrum? - What am I going to do until the next daily scrum? - What are things holding me back, my impediments? |
| Beginning of the Sprint Event | Sprint planning |
| What happens in the Daily Scrum | Team members share their progress, plans, and issues. |
| Sorting items in the product backlog | Based on the descending priority. |
| What do Story Points associated with a user story indicate? | Estimation of complexity of a user story. |
| How do you show the App Directory? | Via App Menu |
| Clean Directory | a new app that is opened for the first time of an App Directory |
| Javascritsource folder | modules in which actual JavaScript actions are defined for nanoflows |
| Javasource Folder | It contains all java sources belonging to microflows in that module |
| Actions folder | the destination folder for all java actions created in that specific module and the only file in it is VerifyPassword.Java |
| Datasets folder | destination folder for all data sets created in that specific module. |
| How to Create a DataSet? | -Rechtermuisknop op MyFirstModule -Add Other -Dataset After Creation, your app directory needs to be synchronized with the open model -Open App Menu -Synchronize App Directory Or press F4 |
| Proxies folder | The proxies folder resembles all the entities, persistent and non-persistent, and all enumerations. |
| what folders are there in the Proxies Folder? | Microflow folder Constant folder |
| Resources folder | Files like HTML files or configuration files, that have a direct effect on the way the application works. It |
| Example of a Mendix Module that uses the Resource Folder | SAML module and Deeplink Module |
| Theme folder | You will find files and folders that together form the source for the styling of your application. |
| Userlib folder | java libraries that could be supporting your custom java functions. |
| Widgets folder | Contains only find files that have the extension .mpk. These files reflect the widgets available in Studio Pro. |
| .mpr | required by Studio Pro to open the app. |
| .mpr bak file | backup file for the .mpr file for restoring your app |
| When can the .mpr bak file be used? | during an upgrade of the Mendix version or an update of the Team Server app. |
| .mpr.lock | indicates that this app is currently open in Studio Pro |
| What can lead to changes in the App Directory? | Performing actions from Studio Pro, such as deploying your app, creating a data snapshot, or importing Marketplace modules, |
| Deployment Folder | This folder contains several folders and files needed to facilitate your local database, files saved during application usage, and sources interpreted by Mendix to run the application. |
| Releases folder | When creating deployment packages via the Studio Pro, Mendix will, by default, store those in this folder |
| Packages folder | When creating an app package, Mendix automatically provides you with a location to store these packages -> package.data-snapshot.zip file |
| package.data-snapshot.zip file | generated once you create a snapshot of your data via Studio Pro. This contains a local database that can be reused by your teammates. |
| classpath file | This is a file needed for Eclipse to import your app into this application |
| .app file | This is a file needed for Eclipse to import your app into this application. |
| <root folder> | This is a file needed for Eclipse to import your app into this application |
| Wat zijn Best Practices in de App Directory? | When you uninstall a module, make sure to remove the Java libraries manually from the userlib folder. The content of the resources folder is copied to the model/resources folder in your deployment folder. |
| Which folders contain source information tied to a specific module enabling reuse of this module in another project? | Javascriptsource and Javasource folders |
| VerifyPassword.java file belonging to the System module is stored in which of the JavaSource sub-folders? | Actions |
| Microflows.java file is stored in which sub-folder of JavaSource directory? | Proxies |
| Which of the following sources are typically stored in the Resources folder of the App Directory? | Configuration files, HTML and Java files |
| Files and folders that together form the styling of your application are typically stored in which of the following folders? | Theme |
| TortoiseSVN | allows to keep track of all changes made. Using this tool, you can revert to a specific older version. |
| What happens when you start a new app? | the system automatically suggests creating a repository for your app. |
| What happens with Apps, which are not under version control yet | can be connected to the version-controlled repository at a later stage. |
| Wanneer kan het voorkomen dat je gebruik moet maken van een Version Controlled Repository? | This can happen when you reuse another app or create a copy of an existing one. In this case, Mendix offers you the option Upload to Version Control Server, which can be found under Version Control. |
| History of Apps | allows you to view the changes applied to the app so far. Based on these changes, you can choose a point to which you want to revert your app in case you need to undo some of the newly added functionality. |
| History op Sprintr | the Mendix Developer Portal, from the app page, navigate to Collaborate > Team Server, |
| 4 type events in collaborate Team Server | 1. Commits 2. Created tags 3. Created branch lines 4. Deleted branch lines. |
| Tagged version | is a revision that has been used to build a Mendix deployment package. |
| in the history op Sprint Per line, you will see: | The avatar of the actor A message The date and time The name of the actor who has triggered the event On which line of the app the event was triggered The used Mendix Studio Pro version The revision number after the event The related user stories |
| History in Mendix Studio Pro | Within Mendix Studio Pro, navigate to Version Control > History |
| 2 Type events in History in Mendix Studio Pro | Commits & created branch line |
| in the history in Sprint Pro, you will see: | The revision number A symbol, indicating the type of change The author of the event The date of the event The time of the event The message of the event The related user stories The changes in the model The changes on disk (repository) |
| Database in Mendix | Mendix has its own default database that you can use for your local deployment. |
| How can you create a snapshot? | To create a snapshot of your data via Mendix Studio Pro, navigate to the Version control menu -> Add Snapshot of Data The next time you will commit, the whole team can use this database |
| Conflicts | When you are working together on an app, various types of conflicts can emerge that you have to resolve before committing new changes to the Team Server. |
| These conflicts can be related to... | your model (document conflicts) or to other documents that are part of your repository (app conflicts). |
| Where can you see the changes you made while working locally? | Within your application model, you can open changes dock, which lists changes you have made to your local working copy since the last update. |
| Wanneer zie je de wijzigingen van je team members? | Once you update your local working copy with the online version, the changes made by your team members will be downloaded to your local version. |
| Wat moet je doen als er een Conflict optreedt? | You need to resolve this conflict before you can commit, as Mendix Studio Pro enforces committing changes without conflicts. |
| Welke 2 opties heb je bij het oplossen van htet conflict? | Restore conflict using mine / Restore conflict using theirs |
| Modify – Modify | you and your team member modified exactly the same document. Example: renaming a label, setting module role access |
| Modify – Delete | occurs when you are changing an element that someone has removed. Example: someone deletes a column in a DataGrid |
| Welke andere 2 conflicten zijn er ook nog? | when adding the same-named documents (pages, microflows, and other documents) or when importing the same AppStore module. |
| Waarom zou je een oudere versie willen openen? | You might want to open an older version to identify the differences between two revisions of the model or because you want to debug a revision that is published in a live environment |
| Mendix Studio Pro keeps track of all app revisions and saves them automatically. Waar zorgen deze App Revisions voor? | This allows you to open an old version of the app if needed. |
| Hoe kan je een oudere revisie openen? | To open an older revision, you need to create a branch from that revision. Make sure to only use this branch for viewing and analyzing purposes, and don’t make changes to this branch since you already have a number of commits done after that revision |
| Wanneer zou je een nieuwe branch willen maken? | Once your app has been published to production, it might be useful to know how to create a branch. That will allow you to continue the development of functionality without affecting the running app. |
| Hoe kan je een branch line aanmaken? | go to the menu Version Control > Manage branch lines. |
| You have three possible ways to create branches | 1. Revisions of the mainline 2. Revisions of another branch line 3. Tagged verslons |
| Merge changes -> | Commit first |
| Port fix (only available on mainline) | Gives you the option to move certain parts from one of your branch lines to your main line. |
| Advanced merge (available on mainline and branch lines) | allows merging various revisions of the mainline or branch line to the selected type of line, respectively. |
| Merge feature branch (only available on mainline) | This function is used to merge a complete branch into the mainline and is only available on the mainline. |
| Waar staat de Merge Changes here function? | Via the App menu > Merge Changes Here function. |
| Reverse merge changes | In some situations, you need to get back to an older version of the app and revert the changes made. Also, the merged changes can be reversed. |
| Delete a branch | After a branch has been merged to another branch- or mainline, you may want to delete the given branch line. |
| When working in an app with version control, which concept would you use to share your database with your team? | By creating a data snapshot and adding it to the deployment directory of your app |
| What type of conflict occurs when you and your colleague both modified the microflow implementing the delete behavior? | Modify-Modify |
| Which of the below listed definitions can be applied to explain what does a tagged version mean? | A revision that has been used to build a Mx deployment package. |
| Which function is used to merge a complete branch into the mainline and is only available on the main line? | Merge feature branch |
| Which of the below mentioned options can be used to merge revisions into and from all lines, main line or branch line? | Advanced merge |
| Waterfall way of work | where large groups of people work on long-term projects |
| the Agile methodology | suggests forming a small cross-functional team to build an app rapidly. |
| Product Owner | who will be translating business needs into the project backlog items and prioritizing them. |
| Ideal team size | 3 |
| Having such a small team | keeps communication lines short and makes collaboration effective |
| SME's | Depending on the technical challenges the team is facing in their project, it might be necessary to involve Subject Matter Experts (SMEs). Note that SMEs are not accountable for product delivery. It’s the responsibility of the core Scrum team! |
| When do you need a bigger team? | when a company aims to start developing multiple apps |
| Before a Scrum team can start developing.. | they should familiarize themselves with the project. The most important things that should happen are getting an overall picture of the project, the organization, and the people involved |
| What is an important event that should happen during Sprint 0? | Initial Product Backlog Refinement |
| What is the Initial Product Backlog Refinement | ensure that the user stories taken into the first sprint are in a ‘ready’ state, meaning that they can be executed by the members of the Scrum team |
| Hoe lang duurt Sprint 0? | 1 of 2 weken |
| Wat doen de Product Owner and other stakeholders tijdens Sprint 0? | share information about the organization and the app requirements. It’s important to understand the overall picture so you have enough context to understand exactly what needs to be created. |
| make sure to conduct the Product Backlog Refinement meeting to ... | make it clear which user stories will be picked up during the first sprint. |
| Wat zijn de 4 Scrum Events? | 1. Sprint Planning 2. Sprint Review 3. Sprint Retrospective 4. Daily Stand-Up |
| Wat is geen officieel Scrum event maar gebeurd wel vaak? | Product Backlog Refinement |
| Waarvoor gebruikt men de Product Backlog Refinement? | before you start working on any user stories, you need to know what to work on |
Created by:
Angeltje1992