This respository's function is to be the wiki for the organization.
active 2024-08-10 → 2024-09-21 (UTC)
Complete coverage26,667 / 26,667 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-30 (UTC)
Events
321
Pushes
3
Pull requests
0
Issues
60
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 43 days from 2024-08-10 to 2024-09-21. Pushes: 3 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 60 total, peak 13 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| julianrivera35 | 46 | 0 | 0 | 0 |
| JeffersonH0501 | 14 | 0 | 0 | 0 |
| WARRIOR1607 | 3 | 3 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#17JeffersonH05012024-09-21 17:08Prepare Viva Voce presentation
- Issue#6JeffersonH05012024-09-09 02:54MS2: Describe the performed brainstorming process (C2) and the solution(s)that came from it.Please, detail the procedure followed in order to derive the mentioned solutions
- Issue#19JeffersonH05012024-09-09 02:54MS2: Brainstorming process
- Issue#1JeffersonH05012024-09-09 02:54MS2: List the 4problems that you selected in O1.
- Issue#5JeffersonH05012024-09-09 02:54MS2: You should deliver at least 2 Journey maps following the observational methodologies described on O1.
- Issue#7JeffersonH05012024-09-09 02:53MS2: Build one video of the solution prototype (blueprint) and describe itbased on the brainstorming.Everyone must contribute to this process
- Issue#3JeffersonH05012024-09-09 02:53MS2: You have to deliver an interview summar
- Issue#2JeffersonH05012024-09-09 02:53MS2: You have to deliver the interview structureused for each interview
- Issue#4JeffersonH05012024-09-09 02:53MS2: You have to identify 4 complete situations for each interview
- Issue#18JeffersonH05012024-09-09 02:22Ethic component
- Issue#16JeffersonH05012024-09-09 02:22Business model and value proposition for each solution.
- Issue#15JeffersonH05012024-09-09 02:22Functional and quality scenarios for each solution. These scenarios are described using the book’s framework (user action, system response and execution context). At least 12 functional scenarios. At least 12 quality scenarios.
- Issue#14JeffersonH05012024-09-09 02:21VD Map with its respective questions for each solution. Must display all 14 business questions and the data sources on it must be obtainable through the designed solution or are publicly available. . This task will also be graded considering the quality of the provided business questions.
- Issue#13JeffersonH05012024-09-09 02:21Provide a total of 14 business questions using the following restrictions in the description.
- Issue#10julianrivera352024-09-02 15:19Context canvas for each solution. Content specified on MS3-O1 template.
- Issue#11julianrivera352024-09-02 15:18XZ Personas for each solution. You must use the template provided by the course. (At least 3 prospective personas and an Analytics personas in total for the group of 6).
- Issue#12julianrivera352024-09-02 15:18XY Empathy maps for each solution. You must include an answer for the Thinks, Sees, Feels and Does sections relating each answer to the problems that were chosen. (At least 4 empathy maps in total)
- Issue#31julianrivera352024-08-31 04:35MS4: Context Canvas
- Issue#31julianrivera352024-08-31 04:35MS4: Context Canvas
- Issue#28julianrivera352024-08-31 04:33MS4: Problem-Alternative-Solutions (PAS) diagram
- Issue#30julianrivera352024-08-31 04:33MS4: VD Map
- Issue#26julianrivera352024-08-31 04:33MS4: Short Description for the proposed solution
- Issue#27julianrivera352024-08-31 04:32MS4: Create an analytic Persona
- Issue#25julianrivera352024-08-31 04:32MS4: Short Description for the problem selected
- Issue#29julianrivera352024-08-31 04:32MS4: 10 business questions
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.