{"id":3694,"date":"2021-02-08T10:07:01","date_gmt":"2021-02-08T00:07:01","guid":{"rendered":"https:\/\/eisabainyo.net\/weblog\/?p=3694"},"modified":"2021-02-10T19:58:53","modified_gmt":"2021-02-10T09:58:53","slug":"4-easy-proven-ways-to-adopt-agile-in-your-organisation-today","status":"publish","type":"post","link":"https:\/\/eisabainyo.net\/weblog\/2021\/02\/08\/4-easy-proven-ways-to-adopt-agile-in-your-organisation-today\/","title":{"rendered":"4 Easy & Proven Ways to Adopt Agile In Your Organisation Today"},"content":{"rendered":"

The need for agile project management becomes more important than ever as software development increases in complexity and teams are working remotely. From how decisions are made about a technical design of a feature to how teams respond to customers on an outage, and everything in between, having a structured approach helps you manage software delivery teams and deliver customer value with ease and efficiency.<\/p>\n

The 4 easy & proven ways to adopt agile in your organisation today are:<\/p>\n

1) Set up agile ceremonies and cadence<\/h3>\n

The foundational ones to start with are:
\n- Daily standup
\n- Fortnightly planning & estimation
\n- Fortnightly sprint review (demos)
\n- Fortnightly retrospective<\/p>\n

2) Clarify roles & responsibilities<\/h3>\n

Answer these important questions below:
\n- Who\u2019s responsible for the product roadmap?
\n- Who's responsible for the delivery?
\n- Who\u2019s responsible for facilitating the sprint retro?<\/p>\n

3) Document and track progress asynchronously<\/h3>\n

Create best practices and templates<\/a> for the followings so everyone knows what\u2019s expected in each situation:
\n- Decision-Making
\n- Meeting
\n- Solution Proposal
\n- Project Kickoff
\n- Stand-up
\n- Sprint Planning
\n- Sprint Backlog
\n- Sprint Retro
\n- Feature Kickoff
\n- Feature Testing
\n- Feature Rollout
\n- Incident Post-mortem<\/p>\n

Decision-Making<\/strong>
\nTo ensure everyone is aligned and informed about the reasons on a decision, be it a technical design implementation approach, tooling.
\nMeeting<\/strong>
\nNever go into a meeting without an agenda and record the important and necessary information discussed at the meeting, especially decisions, next steps, and actions.
\nSolution Proposal<\/strong>
\nSeek input and encourage contribution from engineers when there is a better way of doing something.
\nProject Kickoff<\/strong>
\nWhen a project is ready to be started, it's important to make sure everyone is on the same page, understands the why of the project and the logistics behind the project.
\nStand-up, Sprint Planning, Sprint Backlog, Sprint\u00a0Retro<\/strong>
\nSeems pretty basic, but agile rituals and principles help teams to stay on track of progress and ship incrementally.
\nFeature Kickoff<\/strong>
\nHow does a team ship a software project incrementally? One way this is done is by adopting a feature-driven development approach.
\nFeature Testing<\/strong>
\nThe feature-driven development approach breaks down a project into multiple features.
\nFeature Rollout<\/strong>
\nThese features may also be known as versions or minimal viable product (MVP). They are often released independently to get early feedback from customers.
\nIncident Post-mortem<\/strong>
\nAt the end of the day, providing reliable software is a number one priority, so learn from past outages and continuously make your software better.<\/p>\n

4) Ship value incrementally<\/h3>\n

At the end of the day, providing reliable software is a number one priority, so learn from past outages and continuously make your software better.<\/p>\n

You can view this video on how to manage software development projects effectively using agile:
\n