digital organisation Flashcards
a project
A project is a temporary effort to create a unique product, service or result. It has a clear start and finish and is done for a specific purpose. The project is made up of different tasks or activities that are related to each other and are planned and executed to reach the project’s goal. As the project moves forward, details about the project’s characteristics will be added and refined as it is better understood
PROJECTS ARE THREATENED BY THESE LAWS AND SYNDROME
- Parkinson’s Law
- A task, phase, project will take the time it got allotted
- Murphy’s Law
- If anything can go wrong, it will go wrong
- Brooks’ Law
- Adding manpower to a late (software) project makes it
later - Student Syndrome
- Only start on a task when the need is the highest
Efficient planning can eliminate those threats
what is agile
Agile is a way of managing projects and developing software that focuses on flexibility, teamwork and making sure the customer is satisfied. It is a method that breaks down the work into small chunks, called iterations, and delivers them frequently. It encourages communication and adaptability to change. Agile is a way to manage projects that allows for flexibility and changes, it is less focused on detailed planning and more on delivering value quickly.
roles in a digital project team
Project board: This is a group of stakeholders who provide oversight and direction for the project. They make decisions and approve changes to the project plan.
Project sponsor: This person is the individual or group who provides funding and support for the project. They are ultimately responsible for the success of the project.
Change manager: This person is responsible for managing and implementing changes to the project plan. They ensure that changes are properly documented and communicated to all stakeholders.
Project manager: This person is responsible for planning, executing, and closing the project. They work closely with the project board and sponsor to ensure the project stays on track.
Business lead: This person represents the business side of the project, and is responsible for ensuring that the project aligns with the organization’s goals and objectives.
Data/tech lead: This person is responsible for ensuring that the project’s technical requirements are met and that the technology used aligns with the organization’s goals and objectives.
Subject matter experts: These are individuals who have specialized knowledge in a particular area that is relevant to the project. They provide guidance and support to the project team.
Champions: These are individuals who promote and support the project within the organization. They help to build support for the project and ensure that stakeholders are aware of its progress.
what is the agile methodology ?
AGILE METHODOLOGY= a way to manage a project by using the agile principles. Each methodology has their own focus on specific principles
ASD = Adaptive software development (adapt process)
AUP = Agile Unified Process
Crystal clear = small teams
DSDM = Dynamic Systems Development Method
FDD = Feature-driven development, An Agile methodology that emphasizes the development of features and the use of modeling techniques to plan and manage the project.
Lean =
SAFe = Scaled Agile Framework): An Agile methodology that is designed for large, complex projects and organizations.
scrum
Xp Extreme Programming): An Agile methodology that emphasizes the use of pair programming, test-driven development, and frequent releases to deliver working software.
what is kanban ?
= Originating from the Toyota Production System (TPS).
Kanban is a method for managing and visualizing workflows, it’s often used in software development but can be applied in any field. It’s based on Lean principles and emphasizes visualizing the flow of work, limiting work in progress, and continuous improvement. Kanban boards are used to visualize the progress of work items and teams can make small changes to their workflow as they learn what works and what doesn’t. It’s commonly used with other Agile methodologies to provide a more flexible approach to project management.
Focus on optimizing the process
The Japanese word “kanban”, meaning “visual board” or a “sign”
main principles of kanban
- Focus on value
- Focus on change instead of plan
- Incremental
- Feedback of users
kanban practices
- Visualize the workflow (Kanban board)
- Limit work in progress (WIP)
- Manage flow
- Make process policies explicit
- Implement feedback loops
- Improve collaboratively
how do you limit work in process
Focus on a smaller set of tasks: less context switching
Highlight blockers & bottlenecks
Encourage culture of “getting things done”
Pulling the work (only when there is capacity)
Managing flow not the people
what is scrum
Scrum is a framework for managing and completing complex projects. It is an Agile methodology that is often used in software development, but can be applied to other fields as well. Scrum is based on the principles of transparency, inspection, and adaptation.
The key elements of Scrum include:
Scrum Team: A cross-functional team of individuals who are responsible for delivering the product or service.
Product Backlog: A prioritized list of requirements for the product or service.
Sprint: A time-boxed period (usually 2-4 weeks) in which the team works to deliver a potentially releasable product increment.
Sprint Planning: A meeting at the start of each sprint in which the team plans the work to be done during the sprint.
Daily Scrum: A daily meeting in which the team members discuss their progress and plan for the next 24 hours.
Sprint Review: A meeting at the end of each sprint in which the team demonstrates the work completed during the sprint and receives feedback.
Sprint Retrospective: A meeting at the end of each sprint in which the team reflects on the sprint and identifies ways to improve the process for the next sprint.
Scrum is designed to be flexible and adaptable, allowing teams to quickly respond to changes and deliver value to their customers.
what are the main principles of scrum ?
- Focus on Delivery
- Open Scope & Scope Freeze
- Time-Boxed Iterations
- Self-Managing Team
- High Transparency
- Continuous Improvement
explain this scrum role : product owner
In Scrum, a Product Owner is a role responsible for maximizing the value of the product and the work of the Development Team. The Product Owner is the voice of the customer and the business, and is accountable for ensuring that the product backlog (a list of features or requirements for the product) is prioritized to best achieve the goals of the project.
explain this scrum role : scrum master
The Scrum Master is responsible for:
Ensuring that the team understands and follows the Scrum framework
Facilitating Scrum ceremonies, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective
Removing any obstacles that prevent the team from meeting its commitments
Coaching the team in Scrum values, practices, and rules
Protecting the team from external interruptions and distractions
Ensuring that the team’s definition of “Done” is consistent and of high quality
Helping the team to improve its process and increase its effectiveness over time.
explain this scrum role : team member
Part of a self-organizing & multi-disciplinary team (typically 5-9 people)
Tracking own progress & signaling impediments (timely)
Actively participating in meetings
Making & Committing on sprint planning, realizing the sprint goal.
Sizing product backlog items
explain the scrum artifacts
Scrum is an Agile framework for managing and completing complex projects. Scrum has three main artifacts:
Product Backlog: A prioritized list of all the features, functions, requirements, and enhancements that are needed for the product or service. It is an ordered list of everything that is known to be needed in the product. It is owned by the Product Owner
Sprint Backlog: A list of items from the product backlog that the development team commits to completing during the next sprint. The sprint backlog is owned by the development team and contains specific tasks needed to complete the items in the product backlog.
Increment: The sum of all the Product Backlog items completed during a Sprint and all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in usable condition and meet the Scrum Team’s definition of “Done.”
