Dickson Alves de Souza’s Post

The key to continuing progress is to focus on the problem, not the people. When you approach challenges with a "why" mindset focusing on the problem than people , you show respect for your team . Remember that , every software will always have a bug at every cycle , but what you learn from that bug makes you different. #ProblemSolving #Teamwork #Respect

Gathering context around the implementation before jumping into the code is crucial. It saves your: • Time • Effort • Credibility If you jump into implementation without fully understanding the context of what you are implementing, you risk jeopardizing your credibility within the team. Implementing things prematurely may lead to redoing the work. Therefore, be cautious: • Ask questions. • Read documentation and discussions. • Share your thoughts before beginning the implementation. #softwareengineering #softwaredevelopment

The #discovery phase reveals all the potential pitfalls and ways to bypass them. At @instinctools, we’ve distilled the process into seven definitive steps 👇 Each of these steps is packed with vital questions designed to steer you clear of blind spots and guide you toward the project’s ultimate success 🚀 > https://lnkd.in/dKNbzCwR #discoveryphase #softwaredevelopment #productengineering #productdevelopment

The #discovery phase reveals all the potential pitfalls and ways to bypass them. At @instinctools, we’ve distilled the process into seven definitive steps 👇 Each of these steps is packed with vital questions designed to steer you clear of blind spots and guide you toward the project’s ultimate success 🚀 > https://lnkd.in/d-gAMHJf #discoveryphase #softwaredevelopment #productengineering #productdevelopment

TOMORROW! Webinar: Notes from the Field: Best Practices Designing Field Data Processes. Thursday, September 21 | 7 PM CET | 1 PM ET | 10 AM PT Sponsored by Fulcrum In this webinar, we'll look at addressing a field project's "jobs to be done" through the lenses of planning and prototyping (before), collection (during), and reporting (after), with the top 5 best practices for each phase. Register: https://lnkd.in/d7Zp8sWE Coleman McCormick, Fulcrum #GeoWeek #fieldwork #dataprocessing

Pivotal Tracker Every project starts with a story, no matter what you're building. Tracker helps your team better develop and keep track of them while they progress from start to delivered.

At Ascendle, our goal is to help you build better products, faster. Watch this short clip to learn more about our approach to software development: https://hubs.ly/Q02B4L-c0 #ascendle #softwaredevelopment #agile #scrum #developmentsuccess

The #discovery phase reveals all the potential pitfalls and ways to bypass them. At @instinctools, we’ve distilled the process into seven definitive steps 👇 Each of these steps is packed with vital questions designed to steer you clear of blind spots and guide you toward the project’s ultimate success 🚀 > https://lnkd.in/esAz828s #discoveryphase #softwaredevelopment #productengineering #productdevelopment

Simplicity is hard. Complexity is easy. Make time to do the hard work! When more upfront effort is put into simplifying the solution early it yields high returns in the work not done further down the roadmap. These returns can be cashed in in the form of iterating or working on other solutions, rather than wrangling newly introduced complexity. #softwareengineering #simplicity

#MVP ?? 🤔 It is a product with just enough features to be usable by early customers who can then provide feedback for future product development. A focus on releasing an MVP means that developers potentially avoid lengthy and unnecessary work. The three elements of an MVP are: A narrow target audience: The MVP should be targeted at a specific group of users who are most likely to be interested in the product. This will help the developers to focus on the features that are most important to these users. Useful functionality: The MVP should have enough functionality to be useful to the target audience. This doesn't mean that it has to have all of the features of the final product, but it should have the core features that will make it valuable to users. Testing and refining prior to launch: The MVP should be tested with real users to get feedback on how it can be improved. This feedback can then be used to refine the product before it is launched to the wider market. But...but....but .... If we are thinking of making a revenue based model that will generate profit for us then we shouldn't be saying that - we want to do an MVP. Let's get this facts and understanding correct. MVP is to validate a concept. Maximum it can achieve Break Even. Nothing after that.