The Agile Daily Standup - AgileDad

24601 is the prisoner number and protagonist of the famous novel "Les Misérables" by Victor Hugo. His real name is Jean Valjean. Throughout the novel, Jean Valjean undergoes a profound transformation from a bitter and hardened criminal to a compassionate and virtuous man. There are several factors that contributed to Jean Valjean's transformation. Firstly, he was shown mercy and kindness by the bishop of Digne, who forgave him for stealing his silverware and gave him a second chance. This act of mercy moved Jean Valjean deeply and inspired him to change his ways. Secondly, Jean Valjean was deeply affected by the suffering of Fantine, a young woman he had promised to care for before she died. This experience opened his eyes to the plight of the poor and vulnerable in society, and he made it his mission to help others in need. Thirdly, the love and trust of Cosette, the orphaned daughter of Fantine whom he adopted, helped Jean Valjean to develop a sense of purpose and responsibility. He became determined to create a better life for Cosette and to protect her from harm. Finally, Jean Valjean was motivated by his own desire for redemption and his belief in the power of personal transformation. He recognized the harm that he had caused in the past and committed himself to living a life of compassion, integrity, and service to others. Through these experiences and the influence of the people around him, Jean Valjean learned to become a better man. He was able to overcome his past mistakes and live a life of meaning and purpose, inspiring others to do the same. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

Agile Story Writing Workshops - The Boundaries - Mike Cohn Hi Lee,This tip continues our series where we go back to the basics of user story writing. This week I want to talk about story writing workshops and boundaries.Think outside the box. Do you hate that phrase as much as I do?It’s become another overdone business cliche. But it also bothers me because creativity often comes from thinking inside the box.I’ve seen this proven time and time again as the difference between a successful story-writing workshop and one that fails to engage participants or to lead to useful insights.For a successful story-writing workshop, the product owner provides a significant objective as the box or boundary within which meeting participants work. The product owner starts the workshop by saying something like, “We’re here today to think about this subset (or chunk) of our product.”When a product owner encourages a story-writing workshop to roam freely over the entire product, the participants will likely write a lot of stories but those stories will lack a cohesive purpose. When the product owner instead focuses the meeting on a single, significant objective, participants tend to find more creative and more valuable solutions to the chosen area of the product.Early in the life of a product, a good significant objective could be on identifying what will be needed to deliver a Minimum Viable Product (MVP).Later story-writing workshops might then focus on identifying a Minimum Marketable Feature or MMF. This is a chunk of functionality that is big enough to be valuable when released but is a subset of what users need.An additional benefit of focusing a story-writing workshop on a significant objective like an MVP or MMF is that these workshops can be done less frequently.I like doing a story-writing workshop about every two to three months. Because my workshops are focused on a significant objective, each workshop identifies enough high value stories that the team does not need to spend much time writing new stories each iteration.Setting a significant objective is an easy way to succeed with agile, How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

What are 6 Agile Leadership Tips To Help Build AWESOME Agile Teams? Encourage Different Perspectives: Contrary to popular belief, teams work best when there are disagreements amongst the members on the best path to solve a problem. In the presence of different opinions and some constructive friction, the solution will be more innovative. Stabilize Teams: In contrast to our typical instinct, keeping a team intact for a long period of time will increase the team’s performance. Furthermore, the team will continue to improve the longer they stay together. Small is Big: Smaller teams promote easy attainment of shared understanding, collaboration, expendient flow to done, and rapid learning. Encourage Face-to-Face Interaction: Face-to-face communication is key for enabling optimal team communication and collaboration. This remains true in spite of today’s advanced remote technology. Enable Self-Organization: Self-organization is not easy to achieve, but it is the best thing you can do to set up a team for success. Serve the Team: Serving the team is not a manager’s first instinct. Often a manager feels the best way to serve the team is to direct them and ensure they do not fail. This actually works against the power and capability of a team by shutting down innovation and self-organizing behavior. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

Defining your Product Vision is the single most important thing for your product success. With direction and purpose, you can overcome any challenge. Product Vision statements are how we clarify and communicate our purpose. They set direction, align and guide development teams towards a common goal. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

What does the agile business analyst (BA) do? The business analyst is part of the POBAFATA and is the key interface between the end user and the product owner. Agile BAs engage with consumers and key users to understand their: working processes needs problems plans for growth technical systems user insights user models Ground rules at Backlog Creation Workshop sessions can include the following: Respect everyone’s opinion Be neutral Don’t make assumptions about requirements Everyone is expected to contribute Unimportant discussions should be limited Discuss the issues, not the people Side discussions during the session should be avoided Be on time and have good time management Write everything and ask for documentation that supports the requirements Have the right key-users Practice active listening Conduct the analysis session After having identified the key participants and the analysis session scheduled, it is time to structure the workshop: Before the session: Prepare the features and write down the identified key participants Define the purpose and desired outcomes at each feature Write down all questions and doubts to be answered If you need specific data or documents, add them to the agenda and send them to the key users to have them prepared for the session. During the session: Follow the agenda Respect the ground rules Identify requirements at each macro feature Identify the personas involved Identify the processes and flows at each macro feature Write down all answers to your questions and doubts Ask everything and go deeper to understand the requirement better After the session: Please list all the macro features and their requirements Identify the personas at each feature Gather all the given information by macro feature and its requirements Draw the flow on paper if it is easier for you, and after, do it on Visio (or other) to attach the Functional Requirements Document Start to write the Functional Requirements Document with user stories and send the first draft to the client to approve, and show that you are aligned with them Document everything Focus on business requirements, not tools How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

Sincerity is the virtue of one who communicates and acts in accordance with the entirety of their feelings, beliefs, thoughts, and desires in a manner that is honest and genuine. It’s the quality of being free from pretense, deceit, or hypocrisy. Competence is the ability to do something successfully or efficiently. the quality or state of having sufficient knowledge, judgment, skill, or strength. The NIH Office of Human Resources describes the difference between competencies and skills as: “Competencies are the knowledge, skills, abilities, and behaviors that contribute to individual and organizational performance. Knowledge is information developed or learned through experience, study, or investigation. Skill is the result of repeatedly applying knowledge or ability.” Character is the mental and moral qualities distinctive to an individual. Your character is your personality, especially how reliable and honest you are.

The Top 4 Benefits From Implementing Agile Improved Customer Satisfaction: Agile methodologies emphasize customer collaboration, enabling teams to develop products that meet customer needs and align with the organisation’s strategic objectives. Faster Delivery: Enable teams to deliver working software or products more frequently, reducing the time to market and improving customer satisfaction. Increased Flexibility: Flexibility and adaptability, enabling teams to respond quickly to changes in requirements or the business environment. Enhanced Collaboration: Collaboration between stakeholders, enabling teams to work together more effectively and align their efforts with the organization’s strategic objectives.

Change or Fail.. The Shocking Importance of Adaptability If you do not change, you will NEVER succeed! Learn more about the shocking need for adaptability in every organization and role!

Strong Leaders Accept Mutual Accountability Do strong leaders let the blame fall on an individual or agile team? How do they handle the issues within the organization in a way where mutual accountability and psychological safety exist? Join V. Lee Henson as we explore the 2 keys that help leaders live, learn, and thrive.

Choose a Different Location Follow Through Circle of Influence & Concern Remember The Future Writing The Unspeakable Expectations Why retrospectives The Constellation Game Discuss The Teams Purpose The Feedback Game