As you approach the final sprints in a project it should be at or close to its minimum viable product (MVP) milestone. In other words, having the required features you set out to include in it.
Ideally, your team’s project will reach MVP status before the final sprint, leaving time to make final corrections, polishing the app, and even adding lower priority features.
But what if the final sprint is looming, but you haven’t yet reached the MVP milestone? Don’t get stressed! Keep following the Agile process which allows you to adjust project scope based on your current situation. …
The start of a team project comes with a lot of excitement and energy. But as it progresses some of the novelty wears off and we notice that team members sometimes loose some of their enthusiasm.
In this respect it’s just like starting a new job. You eager at the beginning because it’s something new and unique, but over time it becomes routine.
Do you want to be an active participant or merely a spectator?
In the middle sprints we often see team members who don’t engage with the rest of the team, don’t complete the tasks they’ve agreed to…
You should have noticed by now that Chingu is a proponent of Agile instead of Waterfall project management. But why?
First, what is Waterfall? It’s simply a linear methodology that divides projects into distinct phases — design, development, testing, & deployment. In this methodology 100% of each phase must be completed and signed off before proceeding to the next phase.
This is simple to understand, and it works quite well for highly regulated projects such as those that must meet strict regulatory requirements. For example, banking application that must meet stringent industry & government regulations.
Sprint 4 — Wednesday
Getting help starts with asking a good question.
Consider these two questions…
Do you see the difference? …
Something every software project faces is that reality sometimes rears its ugly head and punches you right in the nose!
Every team and every team member have moments of uncertainty when their project doesn’t go as planned. This could be the result of a technical problem, a team issue, or the realization that the project is just too complex to complete in the remaining sprints.
Emotions are part of the human experience, but don’t let them dictate your future
But uncertainty doesn’t mean failure is a certainty!!! Uncertainty is your signal to pause, evaluate the situation, and adjust your project…
Achieving your Sprint goals directly depends on what you do at the start of the Sprint. As you can probably guess your sprint should start by:
An important part of the Agile process and the Scrum methodology is taking the time as a team to reflect on how you work together to determine how the team can improve.
The process of reflecting is carried out as part of a retrospective in which the team examines what worked (“glowed”), what needs improvement (“growed”), and is there anything that should be discarded (“throwed”)?
As you work on projects it’s easy to get frustrated and depressed when you hit obstacles.
As projects progress you’ll find yourself encountering design issues with your app, technology issues with libraries and services, and conflict within your team.
These can be distracting and if not handled maturely and openly with the team can lead to the “dark side of the Force”. Namely, questioning why you wanted to become a Software Developer and draining the joy out of it.
If you are having these feelings you aren’t alone! This is just another form of the Impostor Syndrome that hits all…
We all make mistakes and we all encounter problems when developing and testing our projects. There is no shame in this since it’s a fact of every Developers life.
So why is it so hard to ask for help? All too often we tend to view problems as failures when we should be viewing them as opportunities to learn — both for ourselves and those we ask to help us.
There is no shame in asking for help. The only shame is not asking for help sooner!
Asking for help has many positive outcomes including:
Sprint 3 — Wednesday
Risk analysis isn’t something we often think about as being a team building tool. In fact, it’s something we might normally read about if we’re having trouble getting to sleep.
But, it can be quite effective for not just mitigating risk, but also for defusing potentially stressful situations in a team.
One source of stress is a problem with no clear path for resolution
Think about it. Many times stress is the results from a problem which has no clear path for a resolution. The team is confronted at that point of maximum stress with even…