Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This week is the first build sprint of your in-house project build.
Work through your sprint backlog, assigning user stories to members of the team.
In modern DevOps, cloud infrastructures, especially platforms like AWS, GCP, and Azure, play an integral role. These platforms offer robust APIs that enable developers to provision and manage resources dynamically, streamlining operations and costs.
Why use Cloud APIs?
Automation: Scripted provisioning removes manual errors.
Scalability: Dynamically adapt to demand.
Flexibility: Customise per requirements.
Integration: Blend with CI/CD pipelines and other DevOps tools.
Before making any requests to a cloud provider’s API, you need to ensure you have the correct permissions and authentication setup.
Obtaining API Keys or Authentication Tokens:
Cloud providers typically use a combination of access keys, secret keys, or tokens for API authentication.
For AWS: You'll set up IAM (Identity and Access Management) users and grant them permissions. Once set up, you'll be provided with an Access Key ID and Secret Access Key. Detailed AWS IAM Setup Guide
Storing Credentials Securely:
Hardcoding or manually handling credentials can lead to security breaches.
AWS secrets manager is a service that helps you protect access to your applications, services, and IT resources without the upfront infrastructure management. Secrets can be database credentials, passwords, third-party API keys, etc. AWS Secrets Manager Documentation.
Here, you communicate with the cloud service, requesting various operations.
Provisioning: This refers to the allocation or reservation of cloud resources. E.g., Creating an EC2 instance or reserving a new RDS (Relational Database Service) instance in AWS.
Configuration: After provisioning, resources might need additional settings or adjustments. E.g., Adjusting the security group of an EC2 instance or updating the database version in RDS.
Monitoring: Cloud services often provide metrics, logs, or alerts to monitor the health and performance of your resources.
E.g., Using Amazon CloudWatch to get logs from a Lambda function or metrics from an EC2 instance. Cloudwatch documentation
De-provisioning: When a resource is no longer required, it should be terminated or stopped to prevent incurring unnecessary charges.
E.g., Terminating an unused EC2 instance or deleting an obsolete S3 bucket.
Every API call receives a response. Handling these responses correctly is crucial.
Success Responses: Usually, a 2XX HTTP status code (like 200 OK). The response body might contain the details of the newly created resource, confirmation of the action taken, or data you requested.
Error Responses: Cloud APIs can respond with errors for various reasons – rate limits, failed authentication, unavailable resources, etc. For instance, AWS provides detailed error messages within an XML tag in the response. Knowing how to parse and react to these messages is essential. Handling AWS Error Messages
There are no defined spikes for this week.
You're encouraged to continue role circles with those who are playing the same role as you.
You may find that you need to manage spikes within your sprints. Remember to follow .
This week is the first build sprint of your in-house project build.
Work through your sprint backlog, assigning user stories to members of the team.
There are no defined spikes for this week.
You may find that you need to manage spikes within your sprints. Remember to follow the techniques you followed earlier in the programme.
You're encouraged to continue role circles with those who are playing the same role as you.
Your project in Design Week is to create a wireframe in Figma and test it with your Product Owners' user group.
Take ideas from your Definition workshop and the sketches you did there. You can consider the ideas you came up with there as low-fidelity prototypes and with Figma, you'll create a high-fidelity prototype.
Your wireframe should include the main steps of the user journey. Think about which parts of the journey you'd like to get feedback on from your users and prioritise building these.
This week, spikes will be in your project groups.
Use this as an opportunity to read and explore documentation on a new technology that you might need for your project, or to find a definitive answer for some of the "How might we" questions that came up during the definition workshop.
If you are looking into new tech, here's a checklist to keep in mind during your research.
List out your needs, and compare them to a list of the pros and cons of the technology you're looking at.
How popular is it? How well maintained is it?
How good is the documentation? What is the learning curve compared to things you have already used?
Are there good external learning resources? (look into different media types - eg: video)
How much time would go into learning vs implementing?
Does it require payment/ does it have limits on usage that would hinder your project?
This week is the first build sprint of your in-house project build.
Work through your sprint backlog, assigning user stories to members of the team.
There are no defined spikes for this week.
You may find that you need to manage spikes within your sprints. Remember to follow the techniques you followed earlier in the programme.
You're encouraged to continue role circles with those who are playing the same role as you.
This week is the first build sprint of your in-house project build.
Work through your sprint backlog, assigning user stories to members of the team.
There are no defined spikes for this week.
You may find that you need to manage spikes within your sprints. Remember to follow the techniques you followed earlier in the programme.
You're encouraged to continue role circles with those who are playing the same role as you.
Your project in Design Week is to create a wireframe in Figma and test it with your user group.
Take ideas from your Definition workshop and the sketches you did there. You can consider the ideas you came up with there as low-fidelity prototypes and with Figma, you'll create a high-fidelity prototype.
Your wireframe should include the main steps of the user journey. Think about which parts of the journey you'd like to get feedback on from your users and prioritise building these.
This week, spikes will be in your project groups.
Use this as an opportunity to read and explore documentation on a new technology that you might need for your project, or to find a definitive answer for some of the "How might we" questions that came up during the definition workshop.
If you are looking into new tech, here's a checklist to keep in mind during your research.
List out your needs, and compare them to a list of the pros and cons of the technology you're looking at.
How popular is it? How well maintained is it?
How good is the documentation? What is the learning curve compared to things you have already used?
Are there good external learning resources? (look into different media types - eg: video)
How much time would go into learning vs implementing?
Does it require payment/ does it have limits on usage that would hinder your project?
User Research & Usability Testing