DEV Community: Jasmine Monique Lewis

Tech Event Recap | Black Tech NOLA – Creator Summit (11/04/2024)

Jasmine Monique Lewis — Sat, 15 Feb 2025 08:13:05 +0000

Recap of Black Tech NOLA: Creator Summit's tech event on November 4, 2024 in New Orleans focused on artificial intelligence, women in tech, entrepreneurs and creators in music and entertainment.

Black Tech NOLA: Creator Summit Introduction
Vendors and Panels
Panel - Women in AI: Paving the Way for the Future of Work
Panel - Making Waves: Entrepreneurs in Music
Panel - Tech vs Human: Music Business and AI
Panel - Shoot You Shot: Advancing in Film and Media
Conclusion

Greetings & Salutations, Artistikk R3b3lls!

Black Tech NOLA Creator Summit Introduction

NOLAvate Black

On Monday, 4th of November 2024, NOLAvate Black hosted its 7th Black Tech NOLA: Creator Summit in conjunction with New Orleans Tourism & Cultural Fund. NOLAvate Black is the largest Black Tech conference in the New Orleans region. I had the pleasure to attend my first Black Tech NOLA: Creator Summit at Loyola University New Orleans from 8am - 4pm.

Founder

Sabrina N. Short, founder and CEO of NOLAvate Black, is a community organizer and tech advocate.

Vendors and Panels

Vendors

The event consisted of the following vendors:
Idea Village
The City of New Orleans
CGI, Inc.
Oschner
Operation Spark

Before the event began, I visited Idea Village, The City of New Orleans, and Oschner.

Idea Village

I visited Idea Village because I wanted to ask about their entrepreneur programs and fellowships, including IdeaInstitute. Idea Village's representative discussed some application questions and how I can attend Yu-Gi-Oh events and ask questions about customers' needs. Furthermore, the vendors shared that I need to know what problem I am trying to solve. They advised I check their website periodically for the next cohort.

The City of New Orleans

I was interested in our great city's career opportunities. It was my first time participating in a NOLAvate's event, and I was unaware I should have brought my resume. I signed the registration form and collected their business card.

Oschner

I visited Oschner's table to learn about their available employment prospects and acquire cool swag. After speaking with their representatives, I discovered they are Microsoft-based and use .NET for software development.

Panels

The event featured four panels and a keynote presentation. The topics of the panels included:

Women in AI: Paving the Way for the Future of Work
Making Waves: Entrepreneurs in Music
Tech vs. Human: The Music Business and AI
Shoot Your Shot: Advancing in Film and Media

Additionally, the keynote addressed the theme of AI, Creators, and the Digital Revolution. Except for the keynote, I attended each panel. I have provided details of the notes and takeaways I gathered from the panel speakers.

Panel - Women in AI: Paving the Way for the Future of Work

Takeaways

Connection is the new currency.
Build a network that works.
Every opportunity is a step.
The future of AI is bright.

Panel Speakers

Diya Wynn
Jornea Armant
Myra Roldan
Yolanda Williams

Diya Wynn

Background

First desktop computer in 3rd grade as a prize for high academic achievement.
Worked in multiple industries.
Want to make an exacerbated impact.
Want to make a better life for her sons and others.

Barriers in AI

There is not enough diversity, we need to consider all stakeholders.
It does not have the voices and experiences of all stakeholders.
How to bring in the voices that may not sit at the table.
Lack of understanding when using systems.
Do not be afraid of AI. We always had a form of AI in our technology; some may not know they were using it.

What advice would you give on finding supportive networks

If connecting in LinkedIn, in note ask for a 30-minute coffee or virtual convo to make a connection.
Think about your network strategically.
- Who do I need to know?
- How to make a connection with people to help you where you want to go?

Myra

Background

She taught herself how to program in Basic.
Her mother enrolled her in the Puerto Rico school.
It took her 10 years to receive a bachelor's degree. During that time, she had a child young and then a second child.
She did not give up.
She got a nursing degree to help pay for college, so then she could pivot to what she wants—tech.
Good data management became a part of her focus in tech working in hospitals.
1% Latinas work in AI, and 0.98% of Black women in AI globally.

What does she envision AI change workforce over decade

Help businesses integrate AI into their business workflow.
Work to try to build a portfolio for yourself and how to integrate into enterprise systems.
Try to build pipelines.
She helps build use cases.
Learning a programming language, right now Phyton.
Learn how to use and understand algorithms.
If you want hands-on experience, try getting into health or finance.

What advice would you give on finding supportive networks

Find a mentor in a role that is in the role you want.
Find a sponsor. The sponsor owns the relationship. They will advocate for you when you are not in a room.
- This relationship is developed overtime.
- Be consistent.

Yolanda

Background

Developed a knack for SQL while working as a research assistant.
She is skilled in Agile.
Worked at Wal-Mart and volunteered for projects.
- Data Management Transformation in retail for Walmart.
Created the first Center of Excellence.
Skills keep you in demand, and they can take you where you want to go.
Know how to manage teams in AI, strategy, and ROI. Create a case study.
Managed multiple teams in AI.
Learn how to navigate the situations you are in.
Internal Expert on how to get innovation started.
Data is applicable to every type of business.

What advice would you give on finding supportive networks

Do not leave the event without meeting someone new.
Focus in and learn.
Community service with high schoolers.

Panel - Making Waves: Entrepreneurs in Music

Takeaways

Run your own race.
Be authentic about your mission in life and what you are doing.

Panel Speakers

Gina Swanson
Tavia Osbey

Tavia Osbey

Background

Work with Tank and the Bangas, an American musical group based in New Orleans.
Help the vision of the artist come to life.
Teach music management at Loyola.
Older sister.
Degree in Business.
She managed Alfred Banks, an emerging New Orleans rapper, for 6 years.
She believes in quality over quantity.

Introduction to Tank

She wanted to meet Tank because Tank inspired her younger sister.
Sent inspiration quotes to Tank.
A faith quote sent to Tank influenced Tank had quit her job at IHOP.
Tavia was persistent, but not nagging about working with Tank.
Tavia pushed Tank to create a spoken word for the first album.

Tavia's Story

She quit her government job to focus on Tank.

How Tavia became Tank's Manager

Tank would joke and state Tavia is her manager.
Tank paid her with meals at first, then $40 or some amount in cash following a performance.

Business Aspect

Be clear in your communication.
Artists do not understand the process of what it takes to get the artist to the stage.

The Process of Getting Started

Help good people around you.
You get weary as an independent artist.
She was getting weary and lost in the music industry.
Feeling as if she exhausted all the resources she had.

Turning Point

The NPR Tiny Desk performance was a breakthrough for the band.
Tank and Tavia would feel successful if their careers could sustain their lifestyle.

Music Business Treachery

The band did not want to make a certain decision, and business executives called her business partner behind her back.

Technology in Trajectory of Tank and the Bangas

You do not need CDs.
Maximize social media.
Tank stayed true to herself. It might take longer.

Trends

Negative being the new positive.
Do not do what is trendy.
You must get comfortable with who is in the room and not focus on who is not.

Advice

Learn as much as you can.
Get in the field; make mistakes.
In the management position, what you do not know hurts the artist. Seek counsel.
Make technology beneficial to you.
She thinks there need to be laws to protect creatives and artists.
Diversify yourself. Use music as a platform to do it.

Moving Forward with Tank and Technology Usage

Currently, Tank is closed off to tech but now open to it.
See Tank acting on Broadway, and currently she is working on a script.

Panel - Tech vs Human: Music Business and AI

Takeaways

Listeners want more.
Technology will push creatives to be more creative.

Panel Speakers

Darrell Flowers
Donovan Williams
Lou Hill

Darrell Flowers

Background

Network Engineer and Composer, Musician.
Team MFN.

AI Impact

The abundance of technology will be a market for a human made things: AI Content vs Human-Made Content.

Positive

There are good things, such as using it to connect with people to get songs cleared.

Donovan Williams

Background

Founder and working on software for artists to have a manager on the phone.
Co-founder of JammAround, working on Music Max AI.

AI Impact

Technology will force artists to have a relationship with fans.

Positive

Save your craftsman for people who care about it.

Lou Hill

Background

Band: Water Seed.
Right now, music is marginally authentic.

AI Impact

AI forces you to have a brand. The ability to bring yourself to the forefront and a reason why someone should fall in love with you.
Technology will push creatives to be more creative. To have their own identity.
AI cannot create its own identity.
AI has desensitized the audience such as Auto-Tune.
ChartMetrics App: Allows you to see your analytics as a musician.

Positive

Can be able to work faster.
A producer can take on my clients.

Hope for Future

Hope the industry goes back to having A&R.

Panel - Shoot You Shot: Advancing in Film and Media

Takeaways

Human touch is important.
Artificial Intelligence will cause loss of jobs.

Panel Speakers

Angelique Roche
Demetrius Grosse
Terence Rosemore

Angelique Roche

Background

Journalist, Author, Producer and Lawyer.

AI in Work

She talked about how a fair, brown hair white woman was the template to check lightning.
Ask who is making money from the product.

Demetrius Grosse

Background

Actor appearing in 70+ films and television.
Directed a movie.

AI in Work

He thinks the human touch will not leave.
Make sure they are equity in the technology.
AI will cause smaller writers' room.

Terence Rosemore

Background

Writer, Director, and a Storyteller.
Finishing two television shows.
Directed 1 feature film and its own Tubi.
It is the Business of Show.

AI in Work

Better adjust and adapt, instead of trying to erase it.
As storytellers, you can be more productive.
People are losing jobs, especially in visual effects.
If you got something meaningful, it will take time for AI to replicate it.
Learn how technology and business work.

Conclusion

In conclusion, the panelists were knowledgeable and prolific in their domains. Artificial Intelligence is prevalent in our daily lives. As technology advances, we cannot escape AI. Therefore, we must learn to embrace and employ AI to address our problems, while maintaining the importance of human interaction. I enjoyed the event and look forward to attending other NOLAvate Black's tech summits. Furthermore, I recommend tech enthusiasts and entrepreneurs to attend NOLAvate Black's events.

R3b3l with me at GitHub, Medium, Dev Community, and LinkedIn

Signed
The LightBringer
I am the eagle that flies ABOVE.

Jasmine Monique Lewis

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Jasmine Monique Lewis — Fri, 31 Jan 2025 05:59:38 +0000

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Jasmine Monique Lewis ・ Jan 31

#scrum #agile #certification #management

Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction

Jasmine Monique Lewis — Fri, 31 Jan 2025 05:58:16 +0000

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Jasmine Monique Lewis — Fri, 31 Jan 2025 05:45:09 +0000

Study Guide Overview
Scrum Principles
Empirical Process Control
Self-Organization
Collaboration
Value-Based Prioritization
Time-Boxing
Iterative Development
Conclusion

Greetings & Salutations, Artistikk R3b3lls!

Study Guide Overview

In my previous article Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction, I provide a synopsis of the examination, an overview of scrum, its benefits, and impediments. As aforementioned, I am pursuing my SCRUMstudy's Scrum Fundamentals Certification (SFC) to learn how to more sophistically implement the Scrum framework, an agile methodology, into my software and project management projects. In this section, Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Principles, I will outline the six principles of the Scrum framework necessary to pass SCRUMstudy's Scrum Fundamentals Certification.

Note
All Scrum definitions, images, and related text in the Scrum Book of Knowledge (SBOK) 4th Edition are taken from SCRUMstudy, a brand of VMEdu, Inc courses. Content obtained from the SBOK will state the page for reference. This is article is intended for informational and educational purposes.

Study Guide Contents

My SFC Exam Study Guide are comprised of eight sections:

Part I: Introduction
Part II: Principles
Part III: Scrum Aspects
Part IV: Scrum Phases
Part V: Scaling Scrum
Part VI: Glossary
Part VII: Practice Test
- Practice Test 1.1
- Practice Test 1.2
- Practice Test 1.3
Part VIII: Case Study
- Case Study – Phase 1
- Case Study – Phase 2
- Case Study – Phase 3
- Case Study – Phase 4
- Case Study – Phase 5

As I study to complete the SCRUMstudy's Scrum Fundamentals Certification (SFC), I will compile notes into a articles and share them with everyone. Yep-pey :)

Let the page-turning commence!

Scrum Principles

Six Scrum Principles are the foundation on of the Scrum framework and can be applied to any project.

Empirical Process Control
Self-Organization
Collaboration
Value-based Prioritization
Time-boxing
Iterative Development

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 9

Empirical Process Control

Empirical Process Control allows learning through observation and experimentation, a pivotal aspect in the Scrum's framework to complete projects or products when clear and concise upfront planning and details are not present at the beginning or mid-way through product development. This principle emphasizes the core philosophy of Scrum based on three main ideas: transparency, inspection, and adaptation.

Transparency

Transparency allows all aspects of any Scrum process to be viewed by everyone. This ensures information is available throughout the organization and develops an open work culture.

There are three components of Transparency:

Artifacts
Meetings
Information Radiators

There are four types of Artifacts:

Project Vision Statement
Prioritized Product Backlog
Sprint Backlog
Release Planning Schedule

There are five types of Meetings:

Sprint Planning Meetings
Daily Standup Meetings
Sprint Review Meetings
Retrospect Sprint Meetings
Release Planning Meeting

There are three types of Information Radiators:

Sprint Burndown Chart
Scrumboard
Sprint Burnup Chart

Artifacts

Project Vision Statement is viewable by business stakeholders and the Scrum Team.
Prioritized Product Backlog displays prioritized User Stories for everyone to view.
Sprint Backlog lists tasks associated with committed User Stories to be completed by Scrum team in current Sprint.
Release Planning Schedule can coordinate work across multiple Scrum Teams and other business stakeholders.

Meetings

Sprint Planning Meetings allow Scrum Teams to estimate time and commitment needed to deliver priority User Stories and commit to set of User Stories complete for a Sprint.
Daily Standup Meetings conducted during the Conduct Daily Standup process, allows all team members to report their progress of a User Story or Bug from the previous day, what they plan to do, and any impediments preventing from completing task in the current Sprint.
Sprint Review Meetings conducted during the Demonstrate and Validate Sprint process, Scrum Team demonstrates potentially shippable Sprint Deliverables to the Product Owner and business stakeholders.
Retrospect Sprint Meetings conducted after the Sprint Review Meetings on the last day of the Sprint allows the Scrum Team to discuss improvement opportunities for future Sprints.
Release Planning Meeting is conducted to enable the Scrum Team to have an overview of the planned releases and delivery schedule for development of the product.

Information Radiators

Sprint Burndown Chart, Scrumboard, and Sprint Burnup Chart is visible to the Scrum Team to monitor progress.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 22 - 23

Inspection

Inspection in Scrum is depicted through the following:

Scrumboard and other Information Radiators demonstrate the progress of the Scrum Team on completing the tasks in the current Sprint.
Frequent Feedback from the customer and other business stakeholders during the following processes: Develop Epic(s), Create Prioritized Product Backlog, Conduct Release Planning, and Refine Prioritized Product Backlog.
Final Inspection and approval of deliverables by the Product Owner and the customer in Demonstrate and Validate Sprint process.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 24

Adaptation

Adaptation allows the Scrum Core Team and business stakeholders learn through transparency and inspection to adapt by making improvement in their work.

There are multiple opportunities in the Scrum framework for Adaptation, below are six areas for example:

Daily Standup Meetings
Constant Risk Identification
Change Requests
Scrum Guidance
Retrospect Sprint Meetings
Retrospect Project Meetings

Example of Opportunities for Adaptation

In Daily Standup Meetings, Scrum Team members discuss impediments to completing tasks and seeking assistance from other team members. More experienced Scrum Team members mentor less experience in knowledge of the project or technology.
Risk identification is performed and iterated throughout the project. Identified risks become inputs to several Scrum processes including Create Prioritized Product Backlog, Refine Prioritized Product Backlog, and Demonstrate and Validate Sprint.
Change Requests can be created due to improvements which are discussed and approved during the Develop Epic(s), Create Prioritized Product Backlog, and Refine Prioritized Product Backlog processes.
The Scrum Guidance Body interacts with Scrum Team members to offer guidance and provide expertise as required during the Create User Stories, Estimate Tasks, Create Deliverables, and Refine Prioritized Product Backlog processes.
In Retrospect Sprint Meetings agreed actionable improvements are determined based on the outputs from the Demonstrate and Validate Sprint process.
In Retrospect Release Meeting, participants document lessons learned and perform reviews seeking ways to improve processes and address inefficiencies.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 24 – 25

Self Organization

Self-Organization allows team members to deliver greater value because Scrum embraces the idea employees are self-motivated and seek greater responsibility. Scrum's leadership style is "supporting leadership" which focus its needs on the Scrum Team to achieve results.

Within the Initiate phase, the Project Vision is defined in the Create Project Vision process, followed by selecting the Product Owner, Scrum Master and Scrum Team in the Identify Scrum Master and Business Stakeholder(s) and Form Scrum Team processes. The Scrum Core Team collaborate with business stakeholders to Develop Epic(s), an Initiate phase's process and Create User Stories process in Plan and Estimate phase. The team's expertise determines technical and management input necessary to execute planned work of project during the Create Deliverables process in Implement phase.

The Product Owner, Voice of Customer, prioritizes work, and tasks breakdown and estimation is completed by the self-organized Scrum Team during Identify Tasks and Estimate Tasks processes of Plan and Estimate phase. During these processes, the Scrum Team determine their work responsibilities, and assist the Product Owner to identity risks and dependencies. Throughout the Sprint, the Scrum Team interface daily through Daily Standup Meetings to discuss progress, impediments, and need of assistance. The Scrum Team interact with other teams through Scrum of Scrum (SoS) meetings.

Finally, in Review and Retrospect phase's Demonstrate and Validate Sprint process, the Scrum Team and Scrum Master work together to show the product increment created during the Sprint and acceptance of completed deliverables. In Release phase's Ship Deliverables process, work is sent to production. Since the Prioritized Product Backlog arranges User Stories by value of importance, the Product Owner and customer can visualize value created after every Sprint.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles| Page: 27

Identification of Phases: Initiate, Plan and Estimate, Implement, Review and Retrospect, Release

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 15

Benefits of Self-Organization

The benefits of self-organization are the following:

Ownership - collective buy-in and shared pride in work
Motivation – leads to enhanced team performance
Growth – innovative and creative environment
Approach – satisfy requirements with simplest and best techniques

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles| Page: 27

Collaboration

Collaboration is the Scrum Core Team working together and liaising with business stakeholders to create and validate deliverables of the project to meet goals outlined in the Project Vision during the Initiate phase. Cooperation occurs when work product consists of the sum of work efforts of various team members. Collaboration occurs when a team works together to play off each other's inputs to produce a greater product. To achieve full collaboration, establishing trust between team members and between team members and business stakeholders. Collaborative work three core dimensions are awareness, articulation, and appropriation.

Awareness

Individuals working together need to be aware of each other's work.

Articulation

Individuals collaborating must partition work into sections, divide sections among team members, and after work completion, reintegrate work.

Appropriation

Adapt technology to one's own situation; technology may be used in a manner completely different than expected by designers.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 29

Benefits of Collaboration in Scrum Projects

"Customer Collaboration over contract negotiation" is emphasized in The Agile Manifesto written in 2001 by Martin Fowler and Jim Highsmith. The Scrum framework approach is to allow the Scrum Core Team members (Product Owner, Scrum Master, and Scrum Team) collaborate with each other and business stakeholders to create deliverables that provide the greatest possible value to the customer.

Collaboration ensures the following project benefits are realized:

Change Requests are minimized.
Risks are efficiently identified and mitigated.
Efficiency is increased.
Continuous improvement is incorporated.

Change Requests are minimized.

The need for changes due to poorly refined requirements are minimized.

Example
During the Initiate phases' Create Project Vision, Develop Epic(s), and Create Prioritized Product Backlog processes, the Product Owner collaborates with business stakeholders to create the Project Vision, Epic(s), and Prioritized Product Backlog. This ensures clarity for Scrum Core Team members work that is required to complete the project. Through a transparent Prioritized Product Backlog, the Scrum Team collaborates with the Product Owner and business stakeholders to create project deliverables.

The Implement phase's Conduct Daily Standup and Refine Prioritized Product Backlog processes and Review and Retrospect phase's Retrospect Sprint process, provide scope to the Scrum Core Team to discuss what has been completed and collaborate on what needs to be done. Therefore, the number of Change Requests from the customer and rework is minimized.

Risks are efficiently identified and mitigated.

Risks are identified and handled efficiently.

Example
Project risks are identified and assessed during the Initiate phase's Develop Epic(s) process, and Implement phases' Create Deliverables and Conduct Daily Standup processes by the Scrum Core Team members. The Scrum meeting tools such as the Daily Standup Meeting, Sprint Planning Meeting, Prioritized Product Backlog Review Meeting, and other meetings provide opportunities for the team identify and assess risks, as well as to efficiently implement risk responses.

Efficiency is increased.

The true potential of the team is realized.

Example
During Implement phase' Conduct Daily Standup process, it provides an opportunity for the Scrum Team to collaborate and understand each members' strengths and weaknesses. If a team member misses a task deadline, the Scrum Team collaborates to complete the tasks and meet the Sprint targets.

Continuous improvement is incorporated.

Continuous improvement is ensured through lessons learned.

Example
During Review and Retrospect phase's Retrospect Sprint process, the Scrum Team identifies what went well and what did not in the previous Sprint. This allows the Scrum Master to collaborate with the team to enhance their performance for the upcoming Sprint. This will also make collaboration more effective in the next sprint.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 29 – 30

Importance of Colocation in Collaboration

Effective Scrum practices often require high-bandwidth communication, which is best achieved when team members are collocated. Preferred communication methods include face-to-face interactions, decision rooms, scrum boards, wall displays, shared tables, and other options. Co-location enables both formal and informal interactions among team members.

Some of the benefits of co-location include:

Questions are answered promptly.
Issues are resolved immediately.
There is less friction between interactions.
Trust is earned and granted much more quickly.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 31

Collaboration in Distributed Teams

While collocated teams are generally preferred, there are instances when the Scrum Team may be distributed. Scrum team members may work from various physical locations, including different cities or countries, and may also be working from home. Even when teams are collocated, members should have the flexibility to work remotely in case of extenuating circumstances that could affect the team's ability to function effectively in a collocated environment. In such situations, it may be necessary to ensure that Scrum Team members are set up to work effectively while distributed.

Scrum Project Tool

Utilizing a collaborative Scrum project tool is strongly advised to ensure team members work productively, especially when they are not located in the same workplace.

The Scrum Project Tool should ideally offer the following: Clearly define all Scrum roles and provide messaging and collaboration tools for team members to communicate effectively with each other.
Develop and utilize key Scrum artifacts.
Outline the workflow for different Scrum processes in the Initiate, Planning, Implement, Retrospect, and Release phases.
Scale to organization or enterprise levels.
Schedule essential Scrum meetings. These meetings can be arranged using a separate video conferencing tool.
Facilitate easy online communication among Scrum Team members, whether one-on-one or via distributed groups and discussion forums.
Document the lessons learned from retrospectives and similar activities, ensuring that relevant reports are generated in real-time.
Implement automation to ensure that templates and guidance from the Scrum Guidance Body are accessible to all Scrum Teams within the organization.
Allow the Scrum Guidance Body to evaluate Scrum-related practices.
Clone similar projects, Epics, and User Stories to help Scrum Team members reduce time spent on unnecessary or duplicate documentation, while also learning from experiences of similar completed work.

Benefits of using a Scrum Project Tool for distributed teams include the following:

Facilitate Scrum Team members to work anytime and from any location.
Automation of reporting, messaging, scheduling, workflows, and other items.
Implementing standard guidelines throughout the organization by automating the recommendations from the Scrum Guidance Body.
Increased efficiency achieved by reducing time spent on creating repetitive or unnecessary documentation when cloning similar projects.
Collaborating with a more diverse team often brings in local perspectives and experiences.
Fewer logistical challenges compared to those of having all team members in one location.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 31 - 32

Value Based Prioritization

The Scrum framework focuses on delivering maximum business value in the shortest time possible. Prioritization is one of the most effective tools for ensuring the greatest value is achieved quickly. Prioritization is the process of determining what tasks must be done immediately versus those that can be addressed later. The traditional Waterfall model of project management employs a sequential process with multiple levels of task prioritization to manage projects effectively. It uses prioritization matrices to delegate tasks and certain tasks must be completed first to expedite the development process and achieve project goals. It uses prioritization matrices to assign tasks, ensuring that some must be completed first to accelerate the development process and achieve project goals.

The Scrum framework employs Value-based Prioritization as a core principle for adaptability and iterative development, providing structure and functionality for development of product or service. Scrum focuses on delivering a valuable product or service to customers early and continuously. The Product Owner prioritizes User Stories in the Prioritized Product Backlog. After the Product Owner receives business requirements from the customer, they are documented as Epics and User Stories. The Product Owner collaborates with customers and business stakeholders to identify the business requirements that provide the most value. To effectively prioritize user stories, the Product Owner needs to understand what customers want and value, organizing the stories in a list from highest to lowest priority. The processes where the principle of Value-based Prioritization is applied include Initiate phase's Create a Prioritized Product Backlog and Implement phase's Refine Prioritized Product Backlog.

Simultaneously, the Product Owner must collaborate with the Scrum Team to identify project risks and uncertainties, as these may lead to negative consequences. It is important to consider this when prioritizing User Stories using a value-based approach. Additionally, the Scrum Team notifies the Product Owner of any dependencies arising from implementation.

The Product Owner must translate the inputs and needs of project stakeholders to create a Prioritized Product Backlog. Prioritization leads to deliverables that meet customer requirements while maximizing business value in the shortest time possible. While prioritizing the User Stories in the Prioritized Product Backlog, the following three factors are considered:

Value
Risk or uncertainty
Dependencies

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 33 - 34

Time Boxing

Time is one of the most important factors in managing a Scrum project. To address this time constraint, Scrum introduces the concept of Time-boxing. This method involves establishing a predetermined duration for every process and activity within a Scrum project. This approach helps Scrum team members manage their workload effectively, avoiding both excess and insufficient work while preventing wasted time on unclear tasks.

Some advantages of Time-boxing include:

An efficient development process
Reduced overhead
Increased team velocity
More focused team members
Well-prepared individuals

Time-boxing is essential in Scrum, helping to prevent excessive refinement of items. However, it must be applied carefully to avoid demotivating the team and creating a negative environment.

Scrum Time-boxes

Sprint

A Sprint is a time-boxed iteration lasting one to four weeks, facilitated by the Scrum Master, who protects the Scrum Team from obstacles during the Implement phase's Create Deliverables process. During a Sprint, the Scrum Team transforms requirements from the Prioritized Product Backlog into shippable product features. This structure helps prevent scope creep that could affect the Sprint goal. Sprints should be kept as short as possible for flexibility, but long enough to produce a deliverable that the Product Owner can review and approve.

Sprint Planning Meeting

Sprint Planning Meeting is conducted prior to each Sprint as part of the Implement phase's Commit User Stories, Identify Tasks, Estimate Tasks, and Update Sprint Backlog processes. The time allocated for this activity is limited to two hours each week throughout the duration of the Sprint.

The Sprint Planning Meeting has the following objectives:

Objective Definition The Product Owner explains the highest-priority User Stories in the Prioritized Product Backlog to the Scrum Team. The Scrum Team collaborates with the Product Owner and then commits to the User Stories, which define the Sprint goal.
Task Identification and Estimation The Scrum Team decides how to complete the Prioritized Product Backlog items to achieve the Sprint goal, tracking committed User Stories and estimated tasks in the Sprint Backlog.

Daily Standup Meeting

The Daily Standup Meeting is a short daily meeting, Time-boxed to 15 minutes. This meeting is carried out by the Scrum Team as part of the Implement phase's Conduct Daily Standup process. The team meets to share updates on the project by answering these three questions:

What have I done since the last meeting?
What do I plan to do before the next meeting?
What impediments or obstacles (if any) am I currently facing?

Sprint Review Meeting

The Sprint Review Meeting is time-boxed to one hour for each week of the Sprint. During this meeting, held in the Review and Retrospect phase's Demonstrate and Validate Sprint process, the Scrum Team presents the current Sprint deliverables to the Product Owner, who reviews them against the Acceptance Criteria to either accept or reject the completed User Stories.

Retrospect Sprint Meeting

The Retrospect Sprint Meeting is Time-boxed to one hour each week of the Sprint duration during the Retrospect Sprint process of Review and Retrospect phase. In this meeting, the Scrum Team gathers to review and reflect on the current Sprint regarding the processes followed, tools used, collaboration and communication methods, and other relevant aspects of the project. The team reviews what went well and what did not in the previous sprint to learn and improve future sprints. Any identified best practices or improvement opportunities may be added to the Scrum Guidance Body.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 35 - 36

Iterative Development

To achieve the goal of delivering maximum business value in a minimum time span, Scrum application consists of Iterative Development of deliverables. In complex projects, the customer may not have concrete requirements for the product result. The Scrum framework uses an iterative model to ensure that change requests can be included in the product. User Stories may be written throughout the project's duration. At the beginning of the project, User Stories are defined as high-level functionalities referred to as Epics. An Epic is usually too large for teams to complete in a single Sprint; therefore, Epics are broken into smaller User Stories.

During the Implement phase, the complex project is deconstructed during the Refine Prioritized Product Backlog process. In the Plan and Estimate phase, new requirements are added to the Prioritized Product Backlog in the processes of Create User Stories, Estimate User Stories, and Commit User Stories. The Product Owner must understand the project's business justification, ensure an increase in ROI, and deliver value after each Sprint when drafting the Prioritized Product Backlog. The Identify Tasks, Estimate Tasks, and Update Sprint Backlog processes of the Plan and Estimate phase create the Sprint Backlog, which the team uses to create deliverables.

In each Sprint, the Implement phase's Create Deliverables process is used to develop the Sprint’s outputs. The Scrum Master facilitates the team to work most productively and the Scrum Team self-organizes and aims to create the Sprint Deliverables from the User Stories in the Sprint Backlog for each Sprint. Multiple cross-functional teams collaborate in parallel during Sprints to produce potentially shippable solutions after each Sprint in major projects. Following the completion of the Sprint, the Product Owner decides whether to accept or reject the deliverables by the Acceptance Criteria from the Demonstrate and Validate Sprint process in the Review and Retrospect phase.

Because everyone engaged gains a better grasp of what needs to be provided as part of the project and iteratively incorporates these learnings, iterative development has the advantage of allowing for course correction. It reduces the time and effort to complete the product and deliverables are more appropriate for business value.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 38

Conclusion

I highly recommend anyone interested in learning the process of software development or project management to take SCRUMstudy's Scrum Fundamentals Certification (SFC)
exam. In this section, **Scrum Fundamentals Certification (SFC) | Study Notes - Part II : Scrum Principles **, I outlined the six principles of the Scrum framework necessary to pass SCRUMstudy's Scrum Fundamentals Certification.

Until next time: or Until next time: it's not the project, it's the six principles.

R3b3l with me at GitHub, Medium, Dev Community, and LinkedIn

Signed
The LightBringer
I am the eagle that flies ABOVE.

Jasmine Monique Lewis

Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction

Jasmine Monique Lewis — Sat, 04 Jan 2025 04:34:04 +0000

Study Notes Overview
Scrum Fundamentals Certification
Overview of Scrum
Scrum Components
Scrum Principles
Scrum Aspects
Scrum Phases
Scrum Benefits
Conclusion

Greetings & Salutations, Artistikk R3b3lls!

Study Notes Overview

I am pursuing my SCRUMstudy's Scum Fundamentals Certification (SFC). I am taking this course and exam because it introduces the Scrum framework. Scrum is a framework within agile methodology commonly used more than Waterfall. In this article titled Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction, I provide a synopsis of the examination, an overview of scrum, its principles, aspects, phases, benefits, and impediments.

Study Notes Contents

My SFC Exam Study Guide are comprised of seven parts:

Part I: Introduction
Part II: Principles
Part III: Scrum Aspects
Part IV: Scrum Phases
Part V: Scaling Scrum
Part VI: Practice Test
- Practice Test 1.1
- Practice Test 1.2
- Practice Test 1.3
Part VII: Case Study
- Case Study – Phase 1
- Case Study – Phase 2
- Case Study – Phase 3
- Case Study – Phase 4
- Case Study – Phase 5

As I study to complete the SCRUMstudy's Scrum Fundamentals Certification (SFC), I will compile notes into a articles and share them with everyone. Yep-pey :)

Let the page-turning commence!

Scrum Fundamentals Certification

The Scrum Fundamentals Certification (SFC) is an introductory certification for individuals interested in learning project and software development processes using Agile methodology. The SFC is provided by SCRUMstudy – the Global Accreditation Body for Scrum and Agile Certifications. There are not any prerequisites for experience or education to prepare for the course. An additional benefit of acquiring this certification is its valid for a lifetime.

Examination Format

The exam format consists of the following:
Multiple choice
40 questions per exam
One mark awarded for every right answer
No negative marks for wrong answers
30 questions need to be answered correctly to pass
60 minutes duration
Online non-proctored exam
Can be attempted multiple times for free

Examination Topics

The exam format consists of the following:

Scrum Principles
Scrum Aspects
Scrum Phases & Processes
Scaling Scrum

Overview of Scrum

What is Scrum?

Scrum is one of the most popular Agile methodologies. It delivers value throughout a project expeditiously due to its adaptative, iterative, fast, flexible, and effective framework.

Agile Methodologies

Agile methodologies are focused on the four factors:

Value Driven Delivery
Adaptive Planning
Continuous Improvement
Active Stakeholder Engagement

Scum Impediments

A Scrum project involves a collaborative effort to create a new product, service, or other result as defined in the Project Vision Statement. Projects are impacted by impediments that makes it difficult for teams to plan, implement, manage, and deliver. Project impediments include the following:

Time
Cost
Scope
Quality
Resources
Organizational Capabilities
Other limitations

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 2

Scrum Components

Scrum consist of three primary components: principles, aspects, and phases. SCRUMstudy's Scrum Body of Knowledge, SBOK Guide is divided the into three areas:
• Principles (Chapter 2)
• Aspects (Chapters 3 – 7)
• Phases (Chapters 8-– 12)

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 7

Principles

Scrum consists of six principles:
• Empirical Process Control
• Self-Organization
• Collaboration
• Value-based Prioritization
• Time-boxing
• Iterative Development

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 9

Aspects

Scrum consists of five aspects:
• Organization
• Business Justification
• Quality
• Change
• Risk

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 11 - 14

Phases

Scrum consists of five phases:
• Initiate
• Plan and Estimate
• Implement
• Review and Retrospect
• Release

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 15

Scrum Principles

Empirical Process Control

An Empirical Process Control model helps make decisions based on observation and experimentation rather than on detailed upfront planning. It relies on the three main ideas of transparency, inspection, and Adaptation.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 363

Self-Organization

Scrum believes that employees are self-motivated and seek to accept greater responsibility. Hence, they deliver much greater value when self-organized.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 384

Collaboration

Collaboration in Scrum refers to the Scrum Core Team working together and interfacing with the stakeholders to create and validate the deliverables of the project to meet the goals outlined in the Project Vision. Collaboration occurs when a team works together to play off each other’s contributions to produce something greater.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 358

Value-based Prioritization

Scrum, however, uses Value-based Prioritization as one of the core principles that drives the structure and functionality of the entire Scrum framework—it helps projects benefit through adaptability and iterative development of the product or service. More significantly, Scrum aims at delivering a valuable product or service to the customer on an early and continuous basis.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Principles | Page: 33

Time-boxing

Time-boxing refers to setting short periods of time for work to be done. If the work undertaken remains
incomplete at the end of the Time-box, it is moved into a subsequent Time-box. Time-boxes provide the
structure needed for Scrum projects, which have an element of uncertainty, are dynamic in nature, and are prone to frequent changes.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 389

Iterative Development

Iterative Development emphasizes how to better manage changes and build products that satisfy customer needs.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 10

Scrum Aspects

Organization

Organization with Scrum roles fall into two broad categories: core and non-core roles. The Organization aspect of Scrum also addresses the team structure requirements to implement Scrum in large projects, programs, and portfolios.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 11 - 12

Business Justification

Business Justification demonstrates the reasons for undertaking a project. It answers the question “Why is this project needed?” Business justification drives all decision making related to a project.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 357

Quality

Quality is defined as the ability of the completed product or Deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary| Page: 375

Change

Change is inevitable in all projects. A primary principle of Scrum is its acknowledgement that a) stakeholders (e.g., customers, users, and sponsors) do change their minds about what they want and need throughout a project (sometimes referred to as ‘requirements churn’) and b) that it is very difficult, if not impossible, for stakeholders to define all requirements during project initiation.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Change | Page: : 102

Risk

Risk is defined as an uncertain event or set of events that can affect the objectives of a project and may
contribute to its success or failure.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary | Page: 380

Scrum Phases

Initiate

This phase is composed of the processes related to initiation of a project: Create Project Vision, Identify
Scrum Master and Stakeholder(s), Form Scrum Team, Develop Epic(s), Create Prioritized Product Backlog, and Conduct Release Planning.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary| Page: 367

Plan and Estimate

The Plan and Estimate phase consist of processes related to planning and estimating tasks, which include Create User Stories, Estimate User Stories, Commit User Stories, Identify Tasks, Estimate Tasks, and Create Sprint Backlog.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Glossary| Page: 372

Implement

The Implement Phase includes processes related to the execution of the tasks and activities to create a
project’s product.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: 366 | Page: Glossary

Review and Retrospect

The Review and Retrospect phase is concerned with reviewing the deliverables and the work that has been done and determining ways to improve the practices and methods used to do project work. In large organizations.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Review and Retrospect | Page: 241

Release

The Release phase emphasizes delivering the Accepted Deliverables to the customer and identifying,
documenting, and internalizing the lessons learned during the project.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Release | Page: 257

Benefits

16 Benefits

Scrum consist of 16 benefits. The benefits are the following:

Adaptability
Transparency
Continuous Feedback
Continuous Improvement
Continuous Delivery of Value
Sustainable Pace
Early Delivery of High Value
Efficient Development Process
Motivation
Faster Problem Resolution
Effective Deliverables
Customer Centric
High Trust Environment
Collective Ownership
High Velocity
Innovative Environment

Adaptability

Empirical Process Control and Iterative Delivery make projects adaptable and open to incorporating change.

Transparency

All information radiators such as Scrum Board and Sprint Burndown Chart are shared, leading to an open work environment.

Continuous Feedback

Continuous Feedback is provided through the Daily Standup and demonstrate and validate Sprint processes.

Continuous Improvement

The deliverables are improved progressively Sprint by Sprint through the Groom Prioritized Product Backlog process.

Continuous Delivery of Value

Iterative processes enable the continuous delivery of value through the Ship Deliverables process as frequently as the customer requires.

Sustainable Pace

Scrum processes are designed such that the people involved can work at a sustainable pace that they can, in theory, continue indefinitely.

Early Delivery of High Value

The Create Prioritized Product Backlog process ensures that the highest value requirements of the customer are satisfied first.

Efficient Development Process

Time-boxing and minimizing non-essential work leads to higher efficiency levels.

Motivation

The Daily Standup and Retrospect Sprint processes lead to greater levels of motivation among employees.

Faster Problem Resolution

Collaboration and colocation of cross-functional teams lead to faster problem solving.

Effective Deliverables

The create Prioritized Product Backlog process and regular reviews after creating deliverables ensures effective deliverables to the customer.

Customer Centric

Emphasis on business value and having collaborative approach to stakeholders ensures a customer-oriented framework.

High Trust Environment

Conduct Daily Standup and Retrospect Sprint processes promote transparency and collaboration, leading to a high trust work environment ensuring low friction among employees.

Collective Ownership

The Commit User Stories process allows team members to take ownership of the project and their work leading to better quality.

High Velocity

A collaborative framework enables highly skilled cross-functional teams to achieve their full potential and high velocity.

Innovative Environment

The Retrospect Sprint and Retrospect Project processes create an environment of introspection, learning, and adaptability leading to an innovative and creative work environment.

Reference | Scrum Body of Knowledge, SBOK Guide | 4th Edition | Chapter: Introduction | Page: 4

Conclusion

I highly recommend anyone interested in learning the process of software development or project management to take SCRUMstudy's Scrum Fundamentals Certification (SFC) exam. In this section, Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction, I provided a synopsis of the examination, an overview of scrum, its principles, aspects, phases, benefits, and impediments.

Until next time: learning Scrum methodology will assist you in completing all types of projects, not only software applications.

R3b3l with me at GitHub, Medium, Dev Community, and LinkedIn

Signed
The LightBringer
I am the eagle that flies ABOVE.

Jasmine Monique Lewis

New Orleans Writers Workshop Recap | Surprise!, Or How To Get Started (01/28/2023)

Jasmine Monique Lewis — Fri, 22 Nov 2024 22:28:38 +0000

Excerpt

I want to share the activities of a poetry workshop, New Orleans Writers Workshop titled Surprise!, or How To Get Started , I participated in last year. As I perfect my writing craft, I enjoy exploring and learning different mediums of self-expression. At the of age nine, and greatly influenced by hip hop emcees, I became mesmerize by shaping words into images in rhythmic form. However, as an uneducated youth of hip hop culture, I was unaware that rap is poetry to a beat. But, as I matured, I learned to love poetry and what it has to offer the human soul and experience.

Poetry Workshop Introduction
Workshop Activities
Pertinent Takeaways and Quotes
Summary of Workshop Activities
Conclusion

Greetings & Salutations, Artistikk R3b3lls!

Poetry Workshop Introduction

I had the pleasure to participate in New Orleans Writers Workshop titled Surprise!, or How To Get Started taught by poet and professor Brad Richard on January 28, 2023. It was a three-hour session on multi-genre focused on poetry.

Instructor

Brad Richard is a teacher, poet, writer of four poem books, and three chapbooks. He has received numerous awards for his poetry and co-founded and directed the New Orleans New Writers Literary Festival. In addition, Richard founded and directed the Scholastic Art & Writing Awards of South Louisiana.

Brad Richard's Poetry Workshop

During our instructors' poetry workshop, he focused on six activities with an array of poem types, elements, and topics. By focusing on six, we were able to learn a plethora of poetry fundamentals to incorporate in our poems.

Workshop Activities

Each of the six activities allowed us to explore poem types or elements. I have included my own work for each activity to provide an example. Each poem are drafts from the course and are not complete works.

Activity I: One Word, One Poetry Line

The first activity required each participant to choose a word from a strip of paper and make it into a single poetry line.

Important Note

I was close to thirty minutes late; therefore, I missed the opportunity to participate in the first activity.

Activity II: Binary Pattern - If, Then

The second activity was a team of two poets to use a binary pattern. The first poet used the word "If" and the second used "Then".

We took turns using an assigned word "If" or "Then", write a statement, and fold the paper to hide a poet's thoughts. Richard followed to ask each pair to read the statements and state an individuals' favorite pair. This was interesting exercise because it demonstrated how poetry can be creative and crafted from unobvious commonalities.

Inquires and Thoughts

The instructor asked the following inquires and encouraged us to ponder these thoughts.

Question #1

Why is it so hard to be original?

Question #2

How can I say something differently?

Unsimilar Comparisons, Awaken Imagination

Richard stated "as humans we have similar experiences", but "we bring our uniqueness to our poetry." "Mishearing's brings imagination."

I learned that we do not have to grapple with attempting to make our poetry prolific, but consider forming and comparing unsimilar objects. It is through dissimilar comparisons and topics; we awaken our imagination.

Activity III: Anaphora

The third activity's nucleus was to create poetry using an anaphora.

Anaphora

Anaphora is when a series of clauses that begin with the same element. For example, I try, or Why not? I was unknowledgeable of the term anaphora nor how to use it, to create magic through words.

Enjambment

In addition, Richard wanted us to understand, learn, and respect the significance of punction and line endings within a poet's writings. He introduced us to the term: enjambment. We engaged in a class exercise reading a poem, with each student pausing at the end of stanza, punctuation, and couplets. We discussed how pauses and punction changes the flow of a poem.

Activity Example

Our activity required us to choose an anaphora and write for twelve minutes. After our allocated time to write, we volunteered to read. Below I have included my poetry writing for our activity. I choose the anaphora, "I fly".

My "I fly" Anaphora Poem

NOTE: Poem not edited from poetry workshop

I Fly

I fly within systems of solar hoping to learn what I see upon the gust of my arms.
I fly into structures that systems fear seeking the glory of what's to come. If clouds could levitate, I fly beneath their skin as bird swings from south to north.

I fly to yearn of the nights of winds I cried to escape the boundaries forced upon my ancestors. I fly outer the sun so I can gaze upon its heat and beautify my skin.

I fly to walls as I crawl to sniff and smell scents of blood dripping from over-extended workers laying the foundations of isms into a corrupted system. I fly with weakness of others I bore when I slide from the canals of my mother's birth pain.

I fly from institutions who idles I refuse to comply and unto thy shadows of never to be seen. Only If I fly, I choose to dive unto the sea scraping the bottom of fishes I have never seen. Unto the sand of darkness between the skin of heels I learn to swim.

I fly with the sharks and species I learn to live with for I have no other companions, I seek to love. I fly with the weird creatures; I fear so can abide by their environment and not force my will unto their being. Who am I not to fly?

I fly with forces that systems create as I tender to my loves who can't escape. Unto oceans from the sea, bodies of water, shades of birds, passing the eagles, I emerge.

I fly when no one is looking, for I don't know when my wings will break. If I fly, I too, can teach you to fly. I fly amongst the stars unto galaxies that milk don't spoil, and there's no way to taunt me for who I care.

I fly where planets don't exist and we have no name for what we see. I fly surrounding light fusing darkness to colors we have never seen. Who am I not to fly?

I fly beyond hearts who scream with fear. I fly for you who don't know what's to come. I fly for us so we know we can stand in the chair and not jump.

Signed,

The LightBringer

I am the eagle that flies ABOVE.

Jasmine Monique

Creativity & Imagination to my Surprise! | Anaphora

After we wrote our anaphora, Richard requested us to share. I obliged and as I read, I was pleasantly surprised to hear my random thoughts written in twelve minutes created something remarkable. Anytime I write, I tend edit. However, the instructor forbid us and directed us to keep writing. As I read, many of my fellow classmates enjoyed my poem. I was shocked. He encouraged us to continue developing our poem, after the workshop.

Lastly, you may infer from the date of this workshop recap, I did not follow-up with continuing my poem. However, as I write this recap, a year, and a few months after the workshop, I will allocate time to complete it. Yikes!

Activity IV: Reading Poetry, One Stanza @ a Time

The fourth activity centered on reading different types of poetry, one stanza per student, and discussing it.

This activity introduced the class to an array of elements through various poetry. We learned to improve our poetry; we must read different poetry styles by a multiplicity of poets.

Activity V: Three Minute Free Writing

Our fifth writing activity was to free write for three minutes of anything.

Richard provided the following Free Writing Objectives:

Free Writing Objectives

• Don't stop
• Be specific
• Let yourself go
• Keep Going
• Don't focus on complete sentences

The Three Minute Free Writing Exercise included the following items:

Three Minute Free Writing Exercise

• First, spend three minutes whatever come to your mind
• Big or little things, anything that has been on your mind
• Be specific as you can

I composed three ideas for friendship, unemployment, and project synopsis on my resume.

I. Friendship

A friendship I thought would last a long-time involving Magic The Gathering (MTG) and extend to other facets such as discussing ideas or participating in other activities. It abruptly ended via text from my friend when stated I was taking a break from MTG. I thought we could socialize, meet for coffee, or play chess, but he stated if the reason he socialized without someone changes he moves on.

II. Unemployment

I need to complete my unemployment application on LA Hire to receive unemployment.

III. Project Synopsis for Resume

I need to draft a project summary of Puerto Rico Recovery Project while I was working at Blue Streak Technologies to add to my LinkedIn and Resume.

Instructor's Three Unique situations

After we wrote for three minutes selecting our own topics, the instructor provided stated three unique situations. The topics were favorite book, first memory you think of about childhood, and something you want to understand.

Favorite Book

Malcom Gladwell's Outliers because it provides an analysis of winners and losers based on design.

First Memory you think of about Childhood

LaSalle Street court, brick playset with circle crafted holes, we as children can fit and crawl.

Something you want to understand

My Life's Purpose. Why have my life beyond my own decisions fit or even extend, or neither into the universe of Yahweh's Plan?

Activity VI: Zuihitsu

Our sixth and last activity was to write a Zuihitsu poem.

Zuihitsu

Zuihitsu is a poem about thoughts that are associated with a different form of how to connect things.

Our instructor stated we could research Kimiko Han on American Poetry Research for learning Zuihitsu. I have included my Zuihitsu poem, I created doing the workshop as an example. I edited the original poem for grammar errors. After all, I was attempting not to edit myself, and wrote whatever came to mind.

Zuihitsu Activity for Free Writing

NOTE: Poem not edited from poetry workshop

Friends Combat: A Zuihitsu | GitHub

A young woman sits in her chair in front of brown, black stripped L-Shaped desked purchased from Walmart, sits three 12in black monitors abreast monitor holders with steel black holes. Her monitors are black for their blankness is lost in her thoughts. Texting on an Android phone to a lost friendship hoping to maintain some form of connection to the man she texts. Not anything romantic or erotic, strictly platonic.

Unemployed, a productive and sporadic mind, skips neurons fighting her thoughts of misunderstanding. Searching for where do I complete a request for a second chance? LaHire differs from my hands to text a friend now lost in the wind.

Breeze from the window I feel his emptiness of not caring. Tis I have no chance in reconciling with a sociopath. It is okay. She learns intention from someone who share not heart explains more than a wicked player could ever thought.

Thinking about the card shop player, an employee with skin, not same color as his, is an indication of racism marked by his masculinity, fear by the gay. Misconceptions in spaces you are not familiar, yet, not interested nor intrigued by cultures created without you. So quick to judge for they do not fear your presence, why should they if you are who you are?

Even so, your isolation is worrisome. You are who I do not want to be. A fake friend that I never lost. Cardboard with images of water and plains graced with angels and creatures, ones and two, toughness and power, only a Planeswalker know.

Drawing cards for the extra win, beyond the artifacts you cast, legendary skills. ENTER COMBAT!

20 life points starts the race. Which human you will displace? 19 for the poke to a face. Instant to negate negative five, HALT, no win. Stuck at 19 for 18 minutes. Clock of 45 minutes quickly counting down to zero minutes on the clock. Foes' life at 20 remains as it stays. No creature you cast will decrease my life span.

Signed,

The LightBringer

I am the eagle that flies ABOVE.

Jasmine Monique

Creativity & Imagination to my Surprise! | Zuihitsu

I was unknowledgeable of Zuihitsu poems. Many of my classmates and I found this difficult to write attempting to connect associated ideas, but in a unique way. I started with my home office. In addition, I used an experience as my starting point. Nevertheless, I am glad I learned a new poem type I did not learn in high school or college.

Pertinent Takeaways and Quotes

Our instructor provided us with essential takeaways and quotes.

Takeaways

• Patterns and Rules can be your friend
• Structure provides guidance
• What people can do with rules is what makes it different
• Focus on Concrete imaginary
• Give yourself the freedom to write badly

Quotes

Unsure or Quote Author

"Words are making love"

Marvin Bell

"There is no such thing as writer's block, only the fear of writing badly"

Federico Garcia Lorca

"The poet is the professor of the five bodily senses."

Binary Patterns

Richard informed us of these binary patterns to incorporate into our poetry:

If/Then
Question/Answer
Why/Because
When/And when

Summary of Workshop Activities

We worked the following workshop activities:

Repetition in the Anaphora
Binary Pattern in a Sentence
Chants and Luck in a Pairing Activity
All connect with Emotions and Memories
All ignite Imagination and get Creativity going
Work on Memory and get it going

Conclusion

In conclusion, I greatly enjoyed Brad Richard's workshop, Surprise!, Or How To Get Started. I loved Richard's humor and involvement with the class. In our three -hour session, we engaged in beneficial activities to improve and understand different types and approaches to writing poetry. I highly recommend all poets of various expertise to participate in a New Orleans Writers Workshop's classes. You will learn something new and improve your current abilities. Most importantly, I recommend you register for one of Brad Richard's poetry sessions.

Signed
The LightBringer
I am the eagle that flies ABOVE.

M.A.C.S [book]: Mentors, Advisors, Coaches & Sponsors | Chapter 2 - A Tale of Two ‘Mentors’ :: Brush It Off

Jasmine Monique Lewis — Sun, 03 Nov 2024 02:18:19 +0000

Excerpt

For chapter two of our M.A.C.S [book] series, we will focus on Mentors. In A Tale of Two "Mentors", I will demonstrate through parables of my college and entrepreneurship journey, lessons I learned by having two female mentors. Chapter 2 - A Tale of Two "Mentors" is comprising of three separate sub sections: When to Brush Things Off, How or When to Terminate or Take a Break in a Relationship and lastly, The Necessity of Open Communication. In “When to Brush Things Off” section, referred to as Brush It Off, we will discuss why and how not to become immersed in minuscule occurrences and lose sight of having mentorship in your life. A Mentor should be beneficial in your personal and/or professional development. You should have multiple mentors throughout your life because individuals have different skills and expertise. People’s knowledge and experience are not interchangeable; thus, you can learn and acquire a plethora of knowledge and wisdom from others with various backgrounds.

Series Recap
Introduction of Chapter 2-A Tale of Two Mentors
When Others Say It Cant be Done Show Them
Dont Let Others Dissuade You
Determining When to Brush It Off

Greetings & Salutations, Artistikk R3b3lls!

Series Recap

In chapter one, “Roles, Relevance & Realness”, of our series, M.A.C.S [book]: Mentors, Advisors, Coaches & Sponsors, we defined each role, its importance and three authenticity qualities, which determine an effective, healthy and successful M.A.C.S relationship, the ‘C’s.

Introduction of Chapter 2 - A Tale of Two Mentors

For chapter two of our M.A.C.S [book] series, we will focus on M entors. In A Tale of Two "Mentors", I will demonstrate through parables of my college and entrepreneurship journey, lessons I learned by having two female mentors. Chapter 2 - A Tale of Two "Mentors" is comprising of three separate sub sections: When to Brush Things Off, How or When to Terminate or Take a Break in a Relationship and lastly, The Necessity of Open Communication. In “When to Brush Things Off” section, referred to as Brush It Off, we will discuss why and how not to become immersed in minuscule occurrences and lose sight of having mentorship in your life. A M entor should be beneficial in your personal and/or professional development. You should have multiple mentors throughout your life because individuals have different skills and expertise. People’s knowledge and experience are not interchangeable; thus, you can learn and acquire a plethora of knowledge and wisdom from others with various backgrounds.

When to Brush Things Off

In every relationship, situations will arise that affect you based on your values, beliefs or principles. The events can be positive, negative or neutral. I am learning not to dwell on negative events and continue to move forward. With relationships, whether its mentorship, coaching or even friendship, you have to learn when to brush things off, converse, and/or take a break/permanently cease an association. It is a hard and necessary process to grow, learn and be our best self. When circumstances occur in relationships that negatively affect me, for example, hurting my feelings or conflicting with my values, I attempt to use a combination of rationality, intuition, spirituality, personal and others’ experiences to resolve my dilemma.

In this M.A.C.S [book] series, I want my experiences and life lessons to transform and improve your life. You do not have to relive my experiences or mistakes. I share them so you can live and perform better. Using life parables from both relationships, I will demonstrate how and why to brush things off, converse, and take a break or end an association.

Let the page commencing begin!

When Others Say It Cant be Done Show Them

From a Liberal Arts major to a STEAM learner

I enrolled in college as an English major with a decisive dream to attend law school and own/operate a legal practice. However, after an excruciatingly boring internship at New Orleans Civil District Court, I was inspired by my love of Yu-Gi-Oh!, a trading card game revered for its intensive strategy and game mechanics, to create a gamer social network. Ignorant of how to begin, I networked in my business courses and discovered Computer Information Systems, a Computer Science major with a Business Administration minor. Initially my obsession to create a gamer social network was the catalyst for learning Computer Science, however, I became in love with its analytics, creativity, complexity, and utility, especially programming. With tenacity and motivation to fulfill my new dream, I began teaching myself full stack web development. Using books, blogs, and YouTube videos to learn HTML, CSS, PHP, and SQL. Because I lacked internet access at home, I would spend time in between classes and late nights at school, teaching myself full stack.

A Naïve Novice’s Big Dream Pierced with Harsh Words

I met the department chair and would regularly seek assistance and guidance on my software business venture. Anytime I asked, she would help debug errors that I did not understand, guide me in the necessary directions and provide resources. However, as a novice and naïve freshman, teaching myself a computer language the school offered seniors, she would always state to wait until I take higher level courses. Unfazed, I continued studying, learning, and asking. On one occasion, I copied an entire block of code from a beginner's book to learn to get it to work with my database. As legend had it, it did not and I received multiple errors. I attempted debugging, but to no avail. Of course, I asked my mentor for assistance. Frustrated by my impatience to wait until enrolling in the database course, she bluntly stated "You cannot build this. I am telling you; it can't be done." Those words pierced my heart deeper than the death of a beloved mother's weeping for her children. I barely held back tears from streaming down my face.

From Novice to Proficient in Midst of Heartache

For a few days after the occurrence, I was sad, hurt, and disappointed that a department chair would say those words to a Computer Science student. Especially, when we live in a world where billion-dollar companies are created in garages, dorm rooms and high school bedrooms. Nevertheless, I did not let her piercing words prevent me from pursuing my business venture and asking her for assistance. I brushed it off and focused on my goal. Before the beginning of my senior year, I was able to develop the client and server-side of a fully functioning, web content management system on my own! Interestingly, even after that conversation of her disapproval, she was always there and continues to guide me.

Dont Let Others Dissuade You

Parable’s Takeaway

When you are working on endeavors of great magnitude, people will state you cannot accomplish them. Regardless of their education, experience, or credentials. It is either from their own mindset and philosophy or their experiences and limitations that they have set for you or themselves. The department chair was fully capable of developing a social network, after all she holds a doctorate in Computer Science and has worked at high tech companies, Google and Apple, Inc., just to name a few. The problem arose when she thought my inexperience and current programming skills would prevent me. I did not fault her for it, simply because I believed in myself and the vision.

Mentors are people. No different than me or you, however, they possess skills, abilities, knowledge, and resources you may not have at your disposal. Situations will arise in your relationships; however, you must determine if it violates your values, beliefs, and principles.

Lesson #3

Do not let others' words or ideas prevent accomplishing your dreams, goals, and aspirations. Sometimes people will not believe, until you show them.

Determining When to Brush It Off

To determine when to Brush It Off, I ask these questions:

Does it conflict with my values, principles, or beliefs?
Does it cause discomfort and prevent me from the pursuit?
Is it that person’s mindset, hindrance, or personality?

Conclusion

Mentors are individuals that should aid in either your personal and/or professional development. Although they may not agree with everything you believe or aspire to, they should be open and supportive. As aforementioned in my gamer social network story, even though my mentor did not think I possessed the skills to bring my vision to life, she always was available to assist and did not turn me away when I needed her help the most. Sometimes you must Brush It Off and keep moving forward. In life, people will say you cannot accomplish your ideas or put limitations on you; it is your responsibility to believe in yourself and focus on your goals. Do not waste time auguring or explaining, your success will show them.

I hope you all learned not to give up and take initiative on your dreams, regardless if a M entor, A dvisor, C oach or S ponsor, state otherwise. Until next time!

One more thing: with all human relationships, there are two personalities and two characters, yours and theirs; so get your M.A.C.S [book]!

Signed

The LightBringer

I am the eagle that flies ABOVE.

M.A.C.S [book]: Mentors, Advisors, Coaches & Sponsors | Chapter 1 – Roles, Relevance, and Realness

Jasmine Monique Lewis — Fri, 01 Nov 2024 03:33:01 +0000

Excerpt

In our M.A.C.S [book]: Mentors, Advisors, Coaches & Sponsors series, we will define each role, discuss how each role can be instrumental in your entrepreneurship success, and how to locate or identify these people in your life. Throughout the series, I will state important lessons or takeaways that can benefit you. In this first chapter, we will introduce and define our M.A.C.S acronym, its relevance and the three qualities each role must possess to be effective.

Series Introduction
Mentor
Advisor
Coach
Sponsor
References

Greetings & Salutations, Artistikk R3b3lls!

Series Introduction

Throughout my personal and professional life, I have been fortunate to have each one of the M.A.C.S [book]: Mentors, Advisors, Coaches & Sponsors. Rather the relationship was long or short term, I grew both personally and professionally, and learned valuable life lessons that I continue to use today. In a previous experience, I mistakenly selected someone to be my mentor who lacked empathy, compassion, and the ability to mentor. Unknowingly, the individual was more of an advisor than a mentor. After this negative encounter, I do not want other entrepreneurs to fall victim. You can learn or grow from every person that enters your life. It is up to you to convert a negative into a positive. It is imperative that entrepreneurs be able to accurately identify individuals who come into their lives offering guidance or assistance as a M entor, A dvisor, C oach or S ponsor. Being able to identify an individual's role can save you time, heartache, and headache.

Let the page turning commence!

Commonalities to Success

Every successful entrepreneur, from Steve Jobs to Bill Gates, had at least one mentor, advisor, coach, or sponsor in their lives that offered guidance or assistance in the journey to fulfill their purpose. Let us take Steve Jobs for example. Before Steve Job's infamous "reality distortion field", introduction of the iPhone and iPad, Jobs was a young adult trying to navigate this terrain called life. In college, Jobs met his first mentor, Robert Friedland, a future billionaire mining magnate, who would help shape Steve Jobs into a charismatic marketer. [1] During Jobs early twenties and early days of Apple Computer, he was advised by Bill Campbell, a famous Silicon Valley advisor for tech companies. [2] Throughout Jobs successes and failures, he sought direction from others who could assist him in fulfilling his vision of making a "computer for the rest of us". [3]

Rather you are an inspiring, startup and mid-career entrepreneur, you cannot fulfill your dreams or achieve your version of success alone. After all, Apple Computer had two Steves.

As an ode to visionary Steve Jobs and my mentor from a distance, we will call Mentors, Advisors, Coaches, Sponsors: The M.A.C.S [book].

Mentor

What is a Mentor?

A Mentor is someone who offers guidance, assistance, professional and emotional support, and possess skills and/or knowledge you seek. You can think of a mentor as a teacher who takes you by the hand and guides you to your destination. A mentor is a person who models what you seek to perform well or become, listen, provide constructive feedback, and invested in your success and growth. A mentor-mentee (protégé) relationship requires trust, honesty, openness, and mutual respect. Unlike the advisor, coach or sponsor, a mentor must know and understand your dreams and goals. More importantly, a mentor is the person you can express vulnerability by sharing your good, bad, and ugly to, without fear of damaging the relationship.

When I started my entrepreneurship journey, I was not very selective about my mentor. On your journey of entrepreneurship, you will meet people who offer guidance and take an interest in you. Always remember to ask "what does this person get out of this?" and "why have he/she taken an interest in me"?

Significance of a Mentor

Mentors are a support system that every entrepreneur needs to be successful. By having someone who is successful in your industry or craft assist in curtailing your mistakes and identifying improvement areas will allow you to reach your goals in a shorter period.

Lesson #1

You must be extremely selective when determining your mentor.

Advisor

What is an Advisor?

An Advisor, an individual who have experience or success in you craft or industry, who offers advice on a need-to-know basis. The relationship between an advisor and advise is usually formal. When you have specific questions or seeking feedback, advisors play a pivotal role in steering you in a wise direction based on their experience. In addition, advisors can facilitate introductions to vital influencers and shakers in your industry.

When I first coined my idea for a trading card gamer social network in college, I did not know how to begin nor the correct questions to ask to begin. A friend introduced me to a recent graduate of our college who became my advisor for a short period. After I clearly communicated the concept, he allowed me to borrow his computer science book, Beginning PHP5, Apache, and MySQL Web Development. Furthermore, he assisted by demonstrating how to install XAMMP, configuring databases and using my first text editor, Komodo. I would frequently visit him to ask questions and receive assistance. Advisors offer relevant advice when you need guidance.

Significance of an Advisor

Unlike mentors who act as a support system, advisors provide critical guidance to your situations or circumstances.

Coach

What is a Coach?

A Coach is someone who improve performance and results. Unlike advisors who provide direction to specific situations or mentors who are support systems, coaches may or may not have personally experienced your desired results, but are trained to generate outcomes in the domain. Coaches assist in clarifying your goals and improving results.

Significance of a Coach

If you want to improve performance or achieve specific results, coaches have strategies for you to obtain your goals.

Sponsor

What is a Sponsor?

A Sponsor is an individual who possess a high level of influence, achievement, and success. A sponsor can connect you to people who can impact your career and capitulate your trajectory. You only share your good and your best with a sponsor. It is pivotal that you let a sponsor know why you are qualified and the best for the job.

Significance of a Sponsor

If you want to get into the right doors and seat at the necessary tables, a sponsor can connect and vouch for you.

Lesson #2

Sponsors are rare. When you can meet a potential sponsor, always allow them to see you at your best.

The Three C’s

For an effective and successful relationship with each of the M.A.C.S Book roles, the individual must possess these three essential qualities: character, compassion, and commitment.

Character - guided by and have good/moral ethics
Compassion - sincere, understanding and empathy towards you and your dreams
Commitment - dedicated to your growth and achievement

I hope you all learn the role, relevance, and qualities of a Mentor, Advisor, Coach or Sponsor. Until next time!

One more thing: you cannot achieve any success by living on an island, so get your M.A.C.S [book]!

Signed
The LightBringer
I am the eagle that flies ABOVE.

Scrum Framework: The Definition of Done

Jasmine Monique Lewis — Mon, 30 May 2022 03:46:35 +0000

Notes Overview
Five Levels of Planning
Evolution of Product Scope
Definition of Done in Product Development
Variations of Defining Done
Creating a Definition of Done
Definition of Done and the Sprint Goal
The Definition of Done and Empiricism
Course Summary
Conclusion

Greetings & Salutations Earthlings!

Notes Overview

Scrum Framework: The Definition of Done provides an explanation of how to determine a scrum team's definition of done for user stories and bugs. Having a team agreed upon definition of done it permits a Scum team to know when items are releasable. Within a course titled Scrum Framework: Definition of Done, this inguistic-written-works-of-artz {L.WWoA} provides the five levels of planning, the evolution of product scope, the definition of done in product development, variations of defining done, creating a definition of done, the definition of done and the Sprint goal, and lastly, the definition of done and empiricism.

Currently, I work as a software engineer at Blue Streak Technologies located in Baton Rouge, Louisiana sub-contracted with CGI. As a part of our preparation for refining our objectives for Program Increment 16 of the Puerto Rico Disaster Recovery Project, we are permitted to enroll in an online training course within CGI Academia offered by issuer SkillSoft titled SCRUM Quality, Planning, and Completion: The Definition of Done.

On Wednesday, May 15, 2021, I participated in and completed the online training course offered by SkillSoft and have compiled my notes into this linguistic-written-works-of-artz {L.WWoA} titled Scrum Framework: The Definition of Done. As I study and learn about SCRUM agile methodology and framework to implement projects, I will compile notes into a linguistic-written-works-of-artz {L.WWoA} and share them with everyone. Yep-pey :)

Let the page-turning commence!

Five Levels of Planning

Five Levels

Product Vision
Product Roadmap
Release Planning
Iteration Planning
- Definition of Done in the most detail
Daily Planning

Level of Detail

At each level, planning becomes more granular while overall it is big pictures.

Evolution of Product Scope

Story Map (Backbone)

The backbone of product development. It is a high-level understanding and how the user interacts with the system.

Walking Skeleton

Phases of Walking Skeleton

Second level of the Story
Minimum viable product
End-to-end functionality

Definition of Done in Product Development

Product

Defining Done allows the following:

Realistic Expectations
Strong Communication
Differing Opinions
Objective Criteria
Gulf of Evaluation
Wireframes and Prototypes

Purpose of Product Vision

The purpose of the Product Vision defines the following:

Why you are building the product
Benefits the product will bring
Who the product is built for
Common Understanding

Definition of Done Questions to Consider

Are we making the right product?
Are we making the product, right?
- Quality
- Benefits
- Value

Acceptance Criteria

Specific to the User Story
Meets user needs
Addresses need to be done

Acceptance Criteria Prevents

Gold-Plating

Acceptance Criteria Prevents Gold-Plating. Gold-Plating is good intentions leading to problems.

Variations of Defining Done

Done vs Potentially Releasable

Done vs Potentially Releasable is an opportunity for continuous development.

Potentially Releasable Products

Potentially Releasable Products are the following:

Complete
Tested
Deliverable now

Definition of Ready

Ready is a checklist and clarity. Definition of Ready should include the following:

Backlog item is ready for the sprint
INVEST criteria
Work is identified
Team capacity is known
Tests and criteria are established

Creating a Definition of Done

Is the work Done?

The team must reach a shared understanding of Done. Using sticky notes the team defines what is Done. The four phases for a team to determine What is Done are Brainstorming, sorting, and categorizing, Analysis and clarification, and lastly, Defining.

Brainstorm

Generate Ideas

Sort and categorize

Customer Journey

Analysis and clarification

Affinity Diagram

Define

Communicate Progress

Why a clear Definition of Done?

A clear Definition of Done provides five instrumental things:

Iterative effort
Missing or incomplete work
Poorly written Definition of Done
Product increment is not potentially releasable
Never or unfamiliar work

Definition of Done and the Sprint Goal

Defining Done prevents missed sprint goals and finds the root cause of analysis.

Missing the Sprint Goal

Four reasons for missing the Sprint Goal

Unclear product requirements
Hidden work
Incorrect estimates
Lack of transparency

Sprint Retrospective

The Sprint Retrospective permits inspecting and adapting.

The Definition of Done and Empiricism

Three Pillars of Empiricism (Scrum)

Transparency

Information and team members know what is going on in the project

Inspection

Inspect daily
Burndown Chart

Adaptation

React quickly
Sprint Retrospective

Scrum Goals

By establishing sprint goals and assignments of User Stories, Kanban Stories, and Bugs each team member must adhere to their commitment. If a User Story, Kanban Story, or Bug is not completed within a sprint, it can be moved to next. Although you can move a story or bug to the next, it is imperative to complete items to prevent inconsistencies in a Burndown Chart.

Commitment

Achieving the goals of the team

Course Summary

The course Scrum and the Definition of Done provided five essential ideas:

Evolution of the product scope
Impact on product quality
Steps to create a Definition of Done
Relationship with the sprint goal
Three pillars of empiricism

Conclusion

I recommend anyone interested in learning software development or project management learn Scrum framework. In this linguistic-written-works-of-artz {L.WWoA} titled Scrum Framework: The Definition of Done, I provide a synopsis of my notes compiled while taking a course within refining Program Increment 16 of the Puerto Rico Disaster Recovery Project as a Software Engineer at Blue Streak Technologies.

Until next time: clarifying your team’s definition of done will assist in completing user stories and achieving sprint goals.

R3b3l with me at GitHub, Medium, Dev Community, and LinkedIn

Signed
The LightBringer
I am the eagle that flies ABOVE.

Jasmine Monique Lewis

DEV Community: Jasmine Monique Lewis

Tech Event Recap | Black Tech NOLA – Creator Summit (11/04/2024)

Table of Contents

Black Tech NOLA Creator Summit Introduction

NOLAvate Black

Founder

Vendors and Panels

Vendors

Idea Village

The City of New Orleans

Oschner

Panels

Panel - Women in AI: Paving the Way for the Future of Work

Takeaways

Panel Speakers

Diya Wynn

Background

Barriers in AI

What advice would you give on finding supportive networks

Myra

Background

What does she envision AI change workforce over decade

What advice would you give on finding supportive networks

Yolanda

Background

What advice would you give on finding supportive networks

Panel - Making Waves: Entrepreneurs in Music

Takeaways

Panel Speakers

Tavia Osbey

Background

Introduction to Tank

Tavia's Story

How Tavia became Tank's Manager

Business Aspect

The Process of Getting Started

Turning Point

Music Business Treachery

Technology in Trajectory of Tank and the Bangas

Trends

Advice

Moving Forward with Tank and Technology Usage

Panel - Tech vs Human: Music Business and AI

Takeaways

Panel Speakers

Darrell Flowers

Background

AI Impact

Positive

Donovan Williams

Background

AI Impact

Positive

Lou Hill

Background

AI Impact

Positive

Hope for Future

Panel - Shoot You Shot: Advancing in Film and Media

Takeaways

Panel Speakers

Angelique Roche

Background

AI in Work

Demetrius Grosse

Background

AI in Work

Terence Rosemore

Background

AI in Work

Conclusion

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Jasmine Monique Lewis ・ Jan 31

Scrum Fundamentals Certification (SFC) | Study Guide - Part I: Introduction

Scrum Fundamentals Certification (SFC) | Study Guide - Part II: Scrum Principles

Table of Contents

Study Guide Overview

Study Guide Contents

Scrum Principles