**Welcome to the Experimental DailyDispatch.News Development Site!**
Here, we can do some technology experiments and tests.

Let's flip the script for a moment...   

"Agile projects are 28% more successful than traditional projects," said some random website.  
"But in my experience, that's pretty accurate," thought MZ

**Goal:**  
- Craft better automation tools and increase the adoption of these tools within WFCA.  
- Share knowledge to ensure redundancy—so the system thrives even if someone leaves.  
- Enhance your careers through learning new skills.

I’m using some basic AI tools for tasks like extraction and webpage summarization, duplication checks, etc. However, this is still an imperfect system that requires testing and iterations for improvement. AI is useful but imperfect, and this will be a different style of work than what you may be used to.

**Expectations for Development**

1. **Budgeting:**  
   - Understand the time and resources we have.
   - Be realistic about what we can accomplish, given the size of the tasks.

2. **Task Estimation:**  
   - Size of issues will be based on a self-determined point or hour estimation system.
   - What features or ideas bring the most value?
   - How much can we accomplish within the current sprint? Team members should commit to what they believe they can achieve.

3. **Kanban Workflow:**  
   - Document stories (ideas for features) and report bugs/issues in our Asana workspace. Adding tasks to our management system reduces the chance of things slipping through the cracks.
   - Allocate time for new features that bring the most value, either by increasing revenue or saving costs.
   - Participate in at least one weekly/daily standup meeting.

   **Standup Meetings:**  
   - **Check-In:** Discuss what you’ve been working on, what you plan to work on, and report any blockers. Collaborate "offline" so others can continue their work without interruption.
   - **Prioritize:** Together, we’ll determine what’s important and what should take precedence, usually in sprint planning or by the scrum master.

**There are a few ways we can do this:**

1. Go through each issue on the Kanban board and push them to completion, starting with those nearing completion.
2. Discuss what you’ve been working on since the last standup, your plans, and any blockers. Document your progress daily on each task, even if it’s incomplete. This creates automatic, searchable documentation for future team members.

**Purpose:**  
With some guidance and iterations, we should be able to create something that integrates nicely with Daily Dispatch.

**Test the System:**  

**Please note:** Working inside development environments is more complex than you might expect as a user. When we reach a finished product, it will be much easier to use. The end user, for example, will simply download the extension from the Chrome Web Store, without needing to go through these detailed steps.

1. **Start by creating an account on the site (I created your accounts- email me for login info etc).** login here.

2. Then, download the Chrome Extension  / Or find it through the admin : Admin Files **Chrome Extension**  

3. Install it by clicking on Extensions in Chrome.  

4. Turn on Developer Mode.  

5. Unpack the zip file into a folder.  

6. Load the folder to activate the Chrome extension.

7) Select the folder you created :


Congratulations! if you made it this far, your computer has a custom chrome extension we are now developing that you can use to integrate news data into our organization.
Now we can start the next chapter.